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
Using Podman 5 and Podman Machine, which is working great overall, very pleased with the improvements on macOS over Podman 4. I created a machine, then destroyed it and re-created it (to be rootful and maybe increase resources). After re-creating I was not able to access using the podman CLI, got a connection refused error from the ssh connection. docker CLI using the socket worked.
Steps to reproduce the issue
Steps to reproduce the issue
Create and start a default podman machine
Destroy it
Create and start a rootful podman machine
Run podman ps
Describe the results you received
After creating the new machine, podman machine didn't update the default in my ~/.config/containers/podman-connections.json file. It still had the ssh port from my deleted podman machine., registered, so any podman commands would fail. docker commands that used the socket worked, but not podman commands
I manually edited the file to correct the ssh port and that fixed the issue
Describe the results you expected
I expect podman machine to check my connections file and be able to repair it if the machine that podman machine created (and allows me to ssh to) is not listed in this file. Automatic repair would be nice, but a warning and a repair command would be great too.
podman info output
host:
arch: arm64buildahVersion: 1.35.0cgroupControllers:
- cpuset
- cpu
- io
- memory
- pids
- rdma
- misccgroupManager: systemdcgroupVersion: v2conmon:
package: conmon-2.1.10-1.fc39.aarch64path: /usr/bin/conmonversion: 'conmon version 2.1.10, commit: 'cpuUtilization:
idlePercent: 99.97systemPercent: 0.02userPercent: 0.01cpus: 4databaseBackend: sqlitedistribution:
distribution: fedoravariant: coreosversion: "39"eventLogger: journaldfreeLocks: 2035hostname: localhost.localdomainidMappings:
gidmap: nulluidmap: nullkernel: 6.7.7-200.fc39.aarch64linkmode: dynamiclogDriver: journaldmemFree: 5800259584memTotal: 8301965312networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.10.0-1.20240312103946045036.main.18.g8377c0a.fc39.aarch64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.11.0-devpackage: netavark-1.10.1-1.20240319111419242122.main.46.gcc3f35d.fc39.aarch64path: /usr/libexec/podman/netavarkversion: netavark 1.11.0-devociRuntime:
name: crunpackage: crun-1.14.4-1.20240302220834691516.main.10.g64ee22c.fc39.aarch64path: /usr/bin/crunversion: |- crun version UNKNOWN commit: feb70bc2ab11944a6443e4f5d2eb96a22f186b80 rundir: /run/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20240220.g1e6f92b-1.fc39.aarch64version: | pasta 0^20240220.g1e6f92b-1.fc39.aarch64-pasta Copyright Red Hat GNU General Public License, version 2 or later <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.remoteSocket:
exists: truepath: /run/podman/podman.socksecurity:
apparmorEnabled: falsecapabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOTrootless: falseseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: trueserviceIsRemote: trueslirp4netns:
executable: /usr/bin/slirp4netnspackage: slirp4netns-1.2.2-1.fc39.aarch64version: |- slirp4netns version 1.2.2 commit: 0ee2d87523e906518d34a6b423271e4826f71faf libslirp: 4.7.0 SLIRP_CONFIG_VERSION_MAX: 4 libseccomp: 2.5.3swapFree: 0swapTotal: 0uptime: 145h 9m 44.00s (Approximately 6.04 days)variant: v8plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- docker.iostore:
configFile: /usr/share/containers/storage.confcontainerStore:
number: 2paused: 0running: 2stopped: 0graphDriverName: overlaygraphOptions:
overlay.mountopt: nodev,metacopy=ongraphRoot: /var/lib/containers/storagegraphRootAllocated: 106769133568graphRootUsed: 12701028352graphStatus:
Backing Filesystem: xfsNative Overlay Diff: "false"Supports d_type: "true"Supports shifting: "true"Supports volatile: "true"Using metacopy: "true"imageCopyTmpDir: /var/tmpimageStore:
number: 36runRoot: /run/containers/storagetransientStore: falsevolumePath: /var/lib/containers/storage/volumesversion:
APIVersion: 5.0.0-dev-8a643c243Built: 1710720000BuiltTime: Sun Mar 17 20:00:00 2024GitCommit: ""GoVersion: go1.21.8Os: linuxOsArch: linux/arm64Version: 5.0.0-dev-8a643c243
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered:
podman machine init is supposed to fail and error out if, if the a connection with the same name already exists. Not sure why this is not the case for you.
Destroy it
Can you please be specific what commands are used?
Issue Description
Using Podman 5 and Podman Machine, which is working great overall, very pleased with the improvements on macOS over Podman 4. I created a machine, then destroyed it and re-created it (to be rootful and maybe increase resources). After re-creating I was not able to access using the podman CLI, got a connection refused error from the ssh connection. docker CLI using the socket worked.
Steps to reproduce the issue
Steps to reproduce the issue
podman ps
Describe the results you received
After creating the new machine, podman machine didn't update the default in my
~/.config/containers/podman-connections.json
file. It still had the ssh port from my deleted podman machine., registered, so anypodman
commands would fail.docker
commands that used the socket worked, but not podman commandsI manually edited the file to correct the ssh port and that fixed the issue
Describe the results you expected
I expect podman machine to check my connections file and be able to repair it if the machine that podman machine created (and allows me to
ssh
to) is not listed in this file. Automatic repair would be nice, but a warning and a repair command would be great too.podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: