Bug#982288: podman: Can't run caontainers - failed to connect to container's attach socket - fixed!

This was resolved by updating conmon as well as podman. (Older versions of podman/conmon were both truncating the attach socket name to 108 bytes; upgrading one and not the other meant that podman wasn't able to find the socket created by conmon any more). And yeah, my UID is really that high--t

Bug#982288: podman: Can't run caontainers - failed to connect to container's attach socket

Control: tag -1 upstream Control: severity important Control: retitle -1 rootless podman fails with very long uids On Mon, Feb 8, 2021 at 6:09 AM Sam Morris wrote: > Package: podman > Version: 3.0.0~rc2+dfsg1-2+b1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: s...@r

Bug#982288: podman: Can't run caontainers - failed to connect to container's attach socket

Package: podman Version: 3.0.0~rc2+dfsg1-2+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: s...@robots.org.uk After upgrading to podman 3, I can't run any containers any more. $ podman run --rm -it docker.io/library/debian:10 Error: failed to connect to container