Switching default podman connection via Podman Desktop always uses rootless connection about podman-desktop

[benoitf]

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

[odockal]

@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.

[odockal]

@xbabalov @benoitf So, I would like to colaborate a bit on a reproducer:

1. Create a podman machine (with default values) and let it start
2. Assert: Machine is started, the socket connection used is correct: podman system connection ls show default true for podman-machine-default-root connection
3. Stop the machine
4. Create new machine called rootful, also keep all values default (rootful, start now)
5. Assert: Machine is created
6. User is offered a dialog to switch the defautl connection to the rootful machine which was jsut created - accept and confirm
7. Assert: podman system connection ls shows that default true value is at rootful-root connection
   Actual: Default true value is at rootful connection -> which is rootless.

[odockal]

Problem might be the change between podman 4.x and 5.x in the content of the Machine config Json:

podman-desktop/extensions/podman/src/extension.ts

Lines 405 to 414 in db8c457

	const machineConfig = JSON.parse(machineConfigJson);
	// if it's rootful let's update the connection to the rootful one
	if (machineConfig.Rootful) {
	await extensionApi.process.exec(getPodmanCli(), [
	'system',
	'connection',
	'default',
	`${runningMachine.Name}${ROOTFUL_SUFFIX}`,
	]);
	}

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
}

[benoitf]

AFAIK this issue was existing in all previous releases

[odockal]

yes.

[benoitf]

but yes probably related to podman v4 -> v5

[benoitf]

PR opened #7024