1podman-machine-init(1)()                              podman-machine-init(1)()
2
3
4

NAME

6       podman-machine-init - Initialize a new virtual machine
7
8

SYNOPSIS

10       podman machine init [options] [name]
11
12

DESCRIPTION

14       Initialize a new virtual machine for Podman.
15
16
17       Podman  on macOS requires a virtual machine. This is because containers
18       are Linux - containers do not run on any other OS  because  containers'
19       core functionality are tied to the Linux kernel.
20
21
22       podman  machine init initializes a new Linux virtual machine where con‐
23       tainers are run.  SSH keys are automatically generated  to  access  the
24       VM,  and  system connections to the root account and a user account in‐
25       side the VM are added.
26
27
28       By default, the VM distribution is Fedora CoreOS.   Fedora  CoreOS  up‐
29       grades  come out every 14 days and are detected and installed automati‐
30       cally. The VM will be rebooted during the upgrade.  For  more  informa‐
31       tion  on updates and advanced configuration, please see the FCOS update
32       docs here and here.
33
34

OPTIONS

36   --cpus=number
37       Number of CPUs.
38
39
40   --disk-size=number
41       Size of the disk for the guest VM in GB.
42
43
44   --help
45       Print usage statement.
46
47
48   --ignition-path
49       Fully qualified path of the ignition file.
50
51
52       If an ignition file is provided, the  file  will  be  copied  into  the
53       user's  CONF_DIR and renamed.  Additionally, no SSH keys will be gener‐
54       ated nor will a system connection be made.  It is assumed that the user
55       will do these things manually or handle otherwise.
56
57
58   --image-path
59       Fully  qualified path or URL to the VM image.  Can also be set to test‐
60       ing, next, or stable to pull down default image.  Defaults to testing.
61
62
63   --memory, -m=number
64       Memory (in MB).
65
66
67   --now
68       Start the virtual machine immediately after it has been initialized.
69
70
71   --rootful=true|false
72       Whether this machine should prefer rootful (true) or  rootless  (false)
73       container execution. This option will also determine the remote connec‐
74       tion default if there is no existing remote connection configurations.
75
76
77       API forwarding, if available, will follow this setting.
78
79
80   --timezone
81       Set the timezone for the machine and containers.  Valid values are  lo‐
82       cal  or a timezone such as America/Chicago.  A value of local, which is
83       the default, means to use the timezone of the machine host.
84
85
86   --volume, -v=source:target
87       Mounts a volume from source to target.
88
89
90       Create  a  mount.  If  /host-dir:/machine-dir  is  specified   as   the
91       *source:target*,  Podman  mounts host-dir in the host to machine-dir in
92       the Podman machine.
93
94
95       The root filesystem is mounted read-only in the default operating  sys‐
96       tem, so mounts must be created under the /mnt directory.
97
98
99       Default  volume mounts are defined in containers.conf.  Unless changed,
100       the default values is $HOME:$HOME.
101
102
103   --volume-driver
104       Driver to use for mounting volumes from the host, such as virtfs.
105
106

EXAMPLES

108              $ podman machine init
109              $ podman machine init myvm
110              $ podman machine init --rootful
111              $ podman machine init --disk-size 50
112              $ podman machine init --memory=1024 myvm
113              $ podman machine init -v /Users:/mnt/Users
114
115
116

SEE ALSO

118       podman(1), podman-machine(1)
119
120

HISTORY

122       March  2021,  Originally  compiled  by   Ashley   Cui   acui@redhat.com
123       ⟨mailto:acui@redhat.com⟩
124
125
126
127                                                      podman-machine-init(1)()