Closed xbabalov closed 3 weeks ago
hi, what does mean " set its connection to default" what is the command you're executing
By default a machine contains both rootless and rootful socket and one is exposed to the socket on the host, and CLI is using system connection
so toggling system connection to rootless or rootful is possible.
But here I don't know what you did in the steps
@benoitf It should be the dialog that appears in the UI when you are starting the machine that is different from the one that had the connection set (either rootful or rootless) to default.
@xbabalov @benoitf So, I would like to colaborate a bit on a reproducer:
podman system connection ls
show default true
for podman-machine-default-root
connectionrootful
, also keep all values default (rootful, start now)rootful
machine which was jsut created - accept and confirmpodman system connection ls
shows that default true
value is at rootful-root
connection
Actual: Default true
value is at rootful
connection -> which is rootless.Problem might be the change between podman 4.x and 5.x in the content of the Machine config Json: https://github.com/containers/podman-desktop/blob/db8c457226f711a748acf5a87344de01511df3e1/extensions/podman/src/extension.ts#L405-L414
machineConfig.Rootful is undefined with podman v5.
This is new json content:
{
"Created":"2024-04-30T12:57:55.2389544+02:00",
"GvProxy":{
"Debug":false,
"MTU":0,
"LogFile":"",
"PidFile":"",
"SSHPort":0
},
"HostUser":{
"Rootful":true,
"UID":1000,
"HostUserModified":false
},
"LastUp":"2024-04-30T12:59:58.8456202+02:00",
"Mounts":null,
"Name":"podman-machine-default",
"Resources":{
"CPUs":2,
"DiskSize":100,
"Memory":2048,
"USBs":[
]
},
"SSH":{
"IdentityPath":"C:\\Users\\podmanqe\\.local\\share\\containers\\podman\\machine\\machine",
"Port":64572,
"RemoteUsername":"user"
},
"Version":1,
"ImagePath":{
"Path":"C:\\Users\\podmanqe\\.local\\share\\containers\\podman\\machine\\wsl\\podman-machine-default-amd64"
},
"WSLHypervisor":{
"UserModeNetworking":false
},
"Starting":false
}
AFAIK this issue was existing in all previous releases
yes.
but yes probably related to podman v4 -> v5
Bug description
Creating/having a rootless machine makes all previously existing or new rootful machines implicitly rootless when they are used as default connections.
I wrote one way to reproduce but the outcome is the same no matter if the rootless machine was created first, last, or new rootful machine was created and connected after the rootless one. Any rootful machine default connection is always rootless unless manually swapped in CLI.
It can be fixed by deleting all of the machines. After deletion, starting a new rootful machine and setting its connection to default results in a rootful connection. Deleting only the rootless machine does not help.
Operating system
Windows 10
Installation Method
Installer from website/GitHub releases
Version
1.10.0
Steps to reproduce
Relevant log output
No response
Additional context
No response