You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the user to provide an Ansible playbook file on init which will
then be run on boot.
Signed-off-by: Jake Correnti <[email protected]>
Signed-off-by: Brent Baude <[email protected]>
Copy file name to clipboardExpand all lines: docs/source/markdown/podman-machine-init.1.md.in
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,8 @@ is copied into the user's CONF_DIR and renamed. Additionally, no SSH keys are g
80
80
Fully qualified registry, path, or URL to a VM image.
81
81
Registry target must be in the form of `docker://registry/repo/image:version`.
82
82
83
+
Note: Only images provided by podman will be supported.
84
+
83
85
#### **--memory**, **-m**=*number*
84
86
85
87
Memory (in MiB). Note: 1024MiB = 1GiB.
@@ -96,6 +98,14 @@ if there is no existing remote connection configurations.
96
98
97
99
API forwarding, if available, follows this setting.
98
100
101
+
#### **--run-playbook**
102
+
103
+
Add the provided Ansible playbook to the machine and execute it after the first boot.
104
+
105
+
Note: The playbook will be executed with the same privileges given to the user in the virtual machine. The playbook provided cannot include other files from the host system, as they will not be copied.
106
+
Use of the `--run-playbook` flag will require the image to include Ansible. The default image provided will have Ansible included.
107
+
108
+
99
109
#### **--timezone**
100
110
101
111
Set the timezone for the machine and containers. Valid values are `local` or
0 commit comments