containers
/
automation-tests
mirror of https://github.com/containers/automation-tests.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

machine set: document --rootful better 

If you change this option all the containers disappear from the default
connection and socket. Thus it is required to recreate the resources.
Sharing between root and rootless is not possible for various reasons.

Fixes #19936

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This commit is contained in:
Paul Holzinger 2023-10-17 18:09:13 +02:00
parent 5853e2bee9
commit dc705d3702
No known key found for this signature in database
GPG Key ID: EB145DD938A3CAF2
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/source/markdown/podman-machine-set.1.md.in
View File

@ -43,12 +43,17 @@ container execution. This option updates the current podman
remote connection default if it is currently pointing at the specified
machine name (or `podman-machine-default` if no name is specified).
@@option user-mode-networking
Unlike [**podman system connection default**](podman-system-connection-default.1.md)
this option makes the API socket, if available, forward to the rootful/rootless
socket in the VM.
Note that changing this option means that all the existing containers/images/volumes, etc...
are no longer visible with the default connection/socket. This is because the root and rootless
users in the VM are completely separated and do not share any storage. The data however is not
lost and you can always change this option back or use the other connection to access it.
@@option user-mode-networking
## EXAMPLES
To switch the default VM `podman-machine-default` from rootless to rootful: