Open Fatmice opened 2 years ago
Hi @Fatmice! If you try to create a new container based on the Fedora 31 image, does it also work?
Could you, please, post the output of the following? I'd like to check whether the wheel
group is present in the container.
$ podman unshare bash
$ cd $(podman mount pymol)
$ cat /etc/group
@containers/podman-maintainers Sorry for the mass tag (how should I call for your presence?). Would you have any ideas? In the log I see an OCI permission denied
that the user tried to fix by deleting their user containers configuration file. Is that a problem?
@containers/podman-maintainers Sorry for the mass tag (how should I call for your presence?). Would you have any ideas? In the log I see an
OCI permission denied
that the user tried to fix by deleting their user containers configuration file. Is that a problem?
I have not knowningly deleted anything...I don't recall messing with anything in the container
Hi @Fatmice! If you try to create a new container based on the Fedora 31 image, does it also work?
No change in outcome
toolbox create test --verbose --image registry.fedoraproject.org/f31/fedora-toolbox:31
DEBU Running as real user ID 1000
DEBU Resolved absolute path to the executable as /usr/bin/toolbox
DEBU Running on a cgroups v2 host
DEBU Checking if /etc/subgid and /etc/subuid have entries for user ocelot
DEBU Validating sub-ID file /etc/subuid
DEBU Validating sub-ID file /etc/subgid
DEBU TOOLBOX_PATH is /usr/bin/toolbox
DEBU Migrating to newer Podman
DEBU Toolbox config directory is /home/ocelot/.config/toolbox
DEBU Current Podman version is 3.4.4
DEBU Creating runtime directory /run/user/1000/toolbox
DEBU Old Podman version is 3.4.4
DEBU Migration not needed: Podman version 3.4.4 is unchanged
DEBU Setting up configuration
DEBU Setting up configuration: file /home/ocelot/.config/containers/toolbox.conf not found
DEBU Resolving image name
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved image name
DEBU Image: 'fedora-toolbox:34'
DEBU Release: '34'
DEBU Resolving container name
DEBU Container: ''
DEBU Image: 'fedora-toolbox:34'
DEBU Release: '34'
DEBU Resolved container name
DEBU Container: 'fedora-toolbox-34'
DEBU Resolving image name
DEBU Distribution (CLI): ''
DEBU Image (CLI): 'registry.fedoraproject.org/f31/fedora-toolbox:31'
DEBU Release (CLI): ''
DEBU Resolved image name
DEBU Image: 'registry.fedoraproject.org/f31/fedora-toolbox:31'
DEBU Release: '31'
DEBU Resolving container name
DEBU Container: 'test'
DEBU Image: 'registry.fedoraproject.org/f31/fedora-toolbox:31'
DEBU Release: '31'
DEBU Resolved container name
DEBU Container: 'test'
DEBU Checking if container test already exists
DEBU Looking for image registry.fedoraproject.org/f31/fedora-toolbox:31
DEBU Resolving fully qualified name for image registry.fedoraproject.org/f31/fedora-toolbox:31 from RepoTags
DEBU Resolved image registry.fedoraproject.org/f31/fedora-toolbox:31 to registry.fedoraproject.org/f31/fedora-toolbox:31
DEBU Checking if 'podman create' supports '--mount type=devpts'
DEBU 'podman create' supports '--mount type=devpts'
DEBU Checking if 'podman create' supports '--ulimit host'
DEBU 'podman create' supports '--ulimit host'
DEBU Resolving path to the D-Bus system socket
DEBU /home/ocelot canonicalized to /home/ocelot
DEBU Resolving path to the Avahi socket
DEBU Resolving path to the KCM socket
DEBU Resolving path to the pcsc socket
DEBU Checking if /media is a symbolic link to /run/media
DEBU Checking if /mnt is a symbolic link to /var/mnt
DEBU Looking for toolbox.sh
DEBU Found /etc/profile.d/toolbox.sh
DEBU Checking if /home is a symbolic link to /var/home
DEBU Creating container test:
DEBU podman
DEBU --log-level
DEBU error
DEBU create
DEBU --dns
DEBU none
DEBU --env
DEBU TOOLBOX_PATH=/usr/bin/toolbox
DEBU --env
DEBU XDG_RUNTIME_DIR=/run/user/1000
DEBU --hostname
DEBU toolbox
DEBU --ipc
DEBU host
DEBU --label
DEBU com.github.containers.toolbox=true
DEBU --mount
DEBU type=devpts,destination=/dev/pts
DEBU --name
DEBU test
DEBU --network
DEBU host
DEBU --no-hosts
DEBU --pid
DEBU host
DEBU --privileged
DEBU --security-opt
DEBU label=disable
DEBU --ulimit
DEBU host
DEBU --userns
DEBU keep-id
DEBU --user
DEBU root:root
DEBU --volume
DEBU /:/run/host:rslave
DEBU --volume
DEBU /dev:/dev:rslave
DEBU --volume
DEBU /run/dbus/system_bus_socket:/run/dbus/system_bus_socket
DEBU --volume
DEBU /home/ocelot:/home/ocelot:rslave
DEBU --volume
DEBU /usr/bin/toolbox:/usr/bin/toolbox:ro
DEBU --volume
DEBU /run/user/1000:/run/user/1000
DEBU --volume
DEBU /run/avahi-daemon/socket:/run/avahi-daemon/socket
DEBU --volume
DEBU /run/.heim_org.h5l.kcm-socket:/run/.heim_org.h5l.kcm-socket
DEBU --volume
DEBU /media:/media:rslave
DEBU --volume
DEBU /mnt:/mnt:rslave
DEBU --volume
DEBU /run/pcscd/pcscd.comm:/run/pcscd/pcscd.comm
DEBU --volume
DEBU /run/media:/run/media:rslave
DEBU --volume
DEBU /etc/profile.d/toolbox.sh:/etc/profile.d/toolbox.sh:ro
DEBU registry.fedoraproject.org/f31/fedora-toolbox:31
DEBU toolbox
DEBU --log-level
DEBU debug
DEBU init-container
DEBU --gid
DEBU 1000
DEBU --home
DEBU /home/ocelot
DEBU --shell
DEBU /bin/bash
DEBU --uid
DEBU 1000
DEBU --user
DEBU ocelot
DEBU --monitor-host
Created container: test
Enter with: toolbox enter test
[ocelot@yellowtrain ~]$ toolbox enter test
Error: invalid entry point PID of container test
Could you, please, post the output of the following? I'd like to check whether the
wheel
group is present in the container.$ podman unshare bash $ cd $(podman mount pymol) $ cat /etc/group
[ocelot@yellowtrain ~]$ podman unshare bash
[root@yellowtrain ~]# cd $(podman mount pymol)
[root@yellowtrain merged]# cat /etc/group
root:x:0:
bin:x:1:
daemon:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mem:x:8:
kmem:x:9:
wheel:x:10:ocelot
cdrom:x:11:
mail:x:12:
man:x:15:
dialout:x:18:
floppy:x:19:
games:x:20:
tape:x:33:
video:x:39:
ftp:x:50:
lock:x:54:
audio:x:63:
users:x:100:
nobody:x:65534:
dbus:x:81:
utmp:x:22:
utempter:x:35:
input:x:999:
kvm:x:36:qemu
render:x:998:
systemd-journal:x:190:
systemd-coredump:x:997:
systemd-network:x:192:
systemd-resolve:x:193:
tss:x:59:
polkitd:x:996:
dip:x:40:
printadmin:x:995:
gluster:x:994:
rtkit:x:172:
pulse-access:x:993:
pulse-rt:x:992:
pulse:x:171:
brlapi:x:991:
qemu:x:107:
nm-openconnect:x:990:
unbound:x:989:
usbmuxd:x:113:
chrony:x:988:
geoclue:x:987:
avahi:x:70:
pipewire:x:986:
saslauth:x:76:
dnsmasq:x:985:
radvd:x:75:
rpc:x:32:
ssh_keys:x:984:
libvirt:x:983:
openvpn:x:982:
nm-openvpn:x:981:
abrt:x:173:
apache:x:48:
colord:x:980:
rpcuser:x:29:
gdm:x:42:
gnome-initial-setup:x:979:
sshd:x:74:
slocate:x:21:
vboxsf:x:978:
tcpdump:x:72:
ocelot:x:1000:ocelot
systemd-timesync:x:977:
screen:x:84:
jackuser:x:976:
flatpak:x:975:
firebird:x:974:
wbpriv:x:88:
deluge:x:973:
akmods:x:972:
vboxusers:x:971:
power:x:970:
parsec:x:969:
parsec-clients:x:968:parsec
systemd-oom:x:967:
rtlsdr:x:966:
sgx:x:965:
I have not knowningly deleted anything...I don't recall messing with anything in the container
I was referring to this snippet:
[ocelot@yellowtrain ~]$ rm .config/containers/containers.conf
No change in outcome
Then we can most likely cross out a problem with Podman itself.
[root@yellowtrain merged]# cat /etc/group ... wheel:x:10:ocelot ...
Okay, the group is there, so we can also cross out some problem there.
First of all, thank you for the extra info. At this moment I don't have an answer but I'll try to reproduce with a Fedora 31 image. But bare in mind that Fedora 31 is long EOL and can't warrant that much. But it would be great if we got this working.
I don't know when they broke.
:(
First of all, thank you for the extra info. At this moment I don't have an answer but I'll try to reproduce with a Fedora 31 image. But bare in mind that Fedora 31 is long EOL and can't warrant that much. But it would be great if we got this working.
Isn't that the point of a container though? I setup these containers long ago with the environments needed to run that software and it ran fine...until it didn't. It's a self-contained environment that ought to run while things outside it changes. The point is these were setup when Fedora 31 was not EOL.
CONTAINER ID CONTAINER NAME CREATED STATUS IMAGE NAME
228819d3e3ef nuclearcraft 2 years ago exited registry.fedoraproject.org/f31/fedora-toolbox:31
7ae8d51ca24f pymol 2 years ago exited registry.fedoraproject.org/f31/fedora-toolbox:31
I have not knowningly deleted anything...I don't recall messing with anything in the container
I was referring to this snippet:
[ocelot@yellowtrain ~]$ rm .config/containers/containers.conf
This was something that others did to try and get the container running. I remember reading this from some other bug thread on here where they were told to try it.
Just tried to reproduce on Rawhide but to no avail, the container starts. I just realized you're running Fedora 34, so I'll have to rebase first to that version to try to reproduce.
Also, I've noticed you're running Podman v3.4.4 but your rpm is back from Fedora 32 days - podman-1.9.2-1.fc32.x86_64
. What's the story there?
Also, I've noticed you're running Podman v3.4.4 but your rpm is back from Fedora 32 days -
podman-1.9.2-1.fc32.x86_64
. What's the story there?
Doesn't make a difference. There's no story. podman-3:3.4.7-1.fc34.x86_64
doesn't change the outcome.
Hi. I found this issue when my podman-toolbox
package in Debian Testing got upgraded to 0.0.99.3-1. Once I downgraded that package, and that package alone, back to 0.0.99.2-2 I was able to enter my containers once again.
Sorry to jump in but I think I found something when trying to make an image based on OpenSUSE to start:
$ podman unshare bash $ cd $(podman mount pymol) $ cat /etc/group
This will list the groups in the host machine, not the image itself. To get the list of groups in the image you need to use cat etc/group
(notice the missing /
at the start of the path).
The "wheel" group is also missing in the OpenSUSE image, so I had to created a new Containerfile using the image as base and add a RUN groupadd wheel
to make it work.
Hello, I have a very similar problem. Seems something included in the last release, 0.0.99.3, because the previous one (0.0.99.2) works fine. fedora 34 (default) works as expected:
➜ alex@alextop ~ toolbox create
Image required to create toolbox container.
Download registry.fedoraproject.org/fedora-toolbox:34 (500MB)? [y/N]: y
Created container: fedora-toolbox-34
Enter with: toolbox enter
➜ alex@alextop ~ toolbox enter
/bin/sh: line 1: /bin/zsh: No such file or directory
Error: command /bin/zsh not found in container fedora-toolbox-34
Using /bin/bash instead.
⬢[alex@toolbox ~]$ cat /etc/hostname
toolbox⬢[alex@toolbox ~]$
But fedora 35 fails:
Image required to create toolbox container.
Download registry.fedoraproject.org/fedora-toolbox:35 (500MB)? [y/N]: y
Created container: fedora-toolbox-35
Enter with: toolbox enter fedora-toolbox-35
➜ alex@alextop ~ toolbox enter fedora-toolbox-35
Error: invalid entry point PID of container fedora-toolbox-35
➜ alex@alextop ~ toolbox --verbose enter fedora-toolbox-35
DEBU Running as real user ID 1000
DEBU Resolved absolute path to the executable as /usr/bin/toolbox
DEBU Running on a cgroups v2 host
DEBU Checking if /etc/subgid and /etc/subuid have entries for user alex
DEBU Validating sub-ID file /etc/subuid
DEBU Validating sub-ID file /etc/subgid
DEBU TOOLBOX_PATH is /usr/bin/toolbox
DEBU Migrating to newer Podman
DEBU Toolbox config directory is /home/alex/.config/toolbox
DEBU Current Podman version is 3.4.7
DEBU Creating runtime directory /run/user/1000/toolbox
DEBU Old Podman version is 3.4.7
DEBU Migration not needed: Podman version 3.4.7 is unchanged
DEBU Setting up configuration
DEBU Setting up configuration: file /home/alex/.config/containers/toolbox.conf not found
DEBU Resolving image name
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved image name
DEBU Image: 'fedora-toolbox:34'
DEBU Release: '34'
DEBU Resolving container name
DEBU Container: ''
DEBU Image: 'fedora-toolbox:34'
DEBU Release: '34'
DEBU Resolved container name
DEBU Container: 'fedora-toolbox-34'
DEBU Resolving image name
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved image name
DEBU Image: 'fedora-toolbox:34'
DEBU Release: '34'
DEBU Resolving container name
DEBU Container: 'fedora-toolbox-35'
DEBU Image: 'fedora-toolbox:34'
DEBU Release: '34'
DEBU Resolved container name
DEBU Container: 'fedora-toolbox-35'
DEBU Checking if container fedora-toolbox-35 exists
DEBU Inspecting mounts of container fedora-toolbox-35
DEBU Starting container fedora-toolbox-35
DEBU Inspecting entry point of container fedora-toolbox-35
DEBU Entry point PID is a float64
DEBU Entry point of container fedora-toolbox-35 is toolbox (PID=0)
Error: invalid entry point PID of container fedora-toolbox-35
➜ alex@alextop ~ podman logs fedora-toolbox-35
Error: failed to get the current user: user: lookup userid 0: invalid argument
Same error with fedora 36, but fedora 33 works.
Specs:
OS: fedora 34
➜ alex@alextop ~ podman version
Version: 3.4.7
API Version: 3.4.7
Go Version: go1.16.15
Built: Thu Apr 21 19:38:09 2022
OS/Arch: linux/amd64
➜ alex@alextop ~ toolbox --version
toolbox version 0.0.99.3
UPDATE:
I tried 0.0.99.2 downloading the release artifact and compiling it manually
cd src
go build
Doing the same with the downloaded 0.0.99.3 also works, so, seems the problem is related with the rpm
Sorry to jump in but I think I found something when trying to make an image based on OpenSUSE to start:
$ podman unshare bash $ cd $(podman mount pymol) $ cat /etc/group
This will list the groups in the host machine, not the image itself. To get the list of groups in the image you need to use
cat etc/group
(notice the missing/
at the start of the path).
That's a really good point, @jbiason !
@Fatmice do you still have the pymol
container based on Fedora 31 that stopped working? If so, can you please try:
$ podman unshare bash
$ cd $(podman mount pymol)
$ cat etc/group # NB: it doesn't start with a /
...
➜ alex@alextop ~ podman logs fedora-toolbox-35 Error: failed to get the current user: user: lookup userid 0: invalid argument
@Alex-Izquierdo that's https://github.com/containers/toolbox/issues/1001
@Fatmice do you still have the
pymol
container based on Fedora 31 that stopped working? If so, can you please try:$ podman unshare bash $ cd $(podman mount pymol) $ cat etc/group # NB: it doesn't start with a / ...
@debarshiray
[root@yellowtrain merged]# cat etc/group root:x:0: bin:x:1: daemon:x:2: sys:x:3: adm:x:4: tty:x:5: disk:x:6: lp:x:7: mem:x:8: kmem:x:9: wheel:x:10:ocelot cdrom:x:11: mail:x:12: man:x:15: dialout:x:18: floppy:x:19: games:x:20: tape:x:33: video:x:39: ftp:x:50: lock:x:54: audio:x:63: users:x:100: nobody:x:65534: utmp:x:22: utempter:x:35: input:x:999: kvm:x:36: render:x:998: systemd-journal:x:190: systemd-coredump:x:997: systemd-network:x:192: systemd-resolve:x:193: dbus:x:81: systemd-timesync:x:996: ssh_keys:x:995: slocate:x:21: tcpdump:x:72: ocelot:x:1000: tss:x:59: unbound:x:994:
Describe the bug I have two containers with fedora 31 images. None of them can be started. Here is one of them
7ae8d51ca24f pymol 2 years ago exited registry.fedoraproject.org/f31/fedora-toolbox:31
toolbox enter pymol -v
Podman log shows that the container can't be started because
Error: failed to get group for sudo: group for sudo not found
podman start --attach pymol --log-level debug
Expected behaviour Clearly the container ought to work...
Actual behaviour It doesn't work and gives a dubious error that's actually not helpful unless you look at the podman log
Screenshots If applicable, add screenshots to help explain your problem.
Output of
toolbox --version
(v0.0.90+)toolbox version 0.0.99.3
Toolbox package info (
rpm -q toolbox
)toolbox-0.0.99.3-2.fc34.x86_64
Output of
podman version
Podman package info (
rpm -q podman
)podman-1.9.2-1.fc32.x86_64
Info about your OS
Additional context I remember that when I first upgraded to Fedora 34 from 33, that I could still start and enter the two containers that used the fedora 31 image...I don't know when they broke, only recently did I need to run them again and find that they are not working...Not good...
toolbox list -i
podman info