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 <s...@robots.org.uk> wrote: > 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's attach socket: > /run/user/876099160/libpod/tmp/socket/3178d20b8a3a42642dc6a7f32884df47019bc4a2a82af94fe4928b00ed3293c9/attach: > no such file or directory > > The directory /run/user/876099160/libpod/tmp/socket is empty. > It works just fine for me: siretart@x1:/tmp$ podman run --rm -it docker.io/library/debian:10 Trying to pull docker.io/library/debian:10... Getting image source signatures Copying blob b9a857cbf04d done Copying config e7d08cddf7 done Writing manifest to image destination Storing signatures root@55ebd48e763b:/# exit > According to unix(7), socket paths are limited to 108 bytes, but the > path in the error message is slightly longer than that: > > $ echo -n > /run/user/876099160/libpod/tmp/socket/18654637587d169f834095dce40d4812378e0056936974c9b7073ba1ae767bfa/attach > | wc -c > 109 > > Is 876099160 really the uid of your user? That seems absurdly long to me, for me it is '1000'. > Podman had a similar sounding bug a couple of years ago, > <https://bugzilla.redhat.com/show_bug.cgi?id=1641800>, but that was > fixed in podman 0.11.1. > That indeed seems related. Would you mind filing a new bug with this information at https://github.com/containers/podman/issues/new and tell me the bug number? Thanks.
