podman: User running podman segfaults

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

Description

Running podman as user causes crashes.

Steps to reproduce the issue:

podman version

Describe the results you received:

$ podman version
ERRO[0000] open /etc/subuid: no such file or directory  
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x3926000 pc=0xf61a89]

Describe the results you expected:

$ sudo podman version
Version:       0.7.4
Go Version:    go1.10.2
OS/Arch:       linux/amd64

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

(paste your output here)

Output of podman info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

VirtualBox

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 22 (21 by maintainers)

Commits related to this issue

rootless: do not segfault if the parent already died Closes: https://github.com/projectatomic/libpod/issues/1189 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> — committed to giuseppe/libpod by giuseppe 6 years ago
rootless: do not segfault if the parent already died Closes: https://github.com/projectatomic/libpod/issues/1189 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Closes: #1201 Approved by: rh... — committed to containers/podman by giuseppe 6 years ago

Most upvoted comments

Yes, that seems to have been it:

$ echo $USER:10000:65536 | sudo tee /etc/subuid
docker:10000:65536
$ echo $USER:10000:65536 | sudo tee /etc/subgid
docker:10000:65536
$ podman version
Version:       0.7.4
Go Version:    go1.10.2
OS/Arch:       linux/amd64

Same as documented in #1185

afbjorklund on Jul 30, 2018