boydkelly
September 14, 2021, 1:43pm
#1
Thought I would give Fedora 35 Silverblue a try but ran into a glitch right away. Seems none of my toolboxes (33 or 34) will start with the output below. Also podman isn’t listing any images except the toolbox I had tried to start. (There should be a couple dozen there) Of course the nice thing with Silverblue is you can try stuff and back out. Wondering if there is anything reported on this or anything else I needed to do before rebasing.
[bkelly@xps ~]$ podman images ls --all
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/tools 34 8dee601b6e96 7 weeks ago 4.07 GB
[bkelly@xps ~]$
[bkelly@xps ~]$ toolbox -c tools -v enter
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 bkelly
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 /var/home/bkelly/.config/toolbox
DEBU Current Podman version is 3.3.0
DEBU Creating runtime directory /run/user/1000/toolbox
DEBU Old Podman version is 3.3.1
DEBU Migration not needed: Podman version 3.3.0 is old
DEBU Setting up configuration
DEBU Setting up configuration: file /var/home/bkelly/.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:35'
DEBU Release: '35'
DEBU Resolving container name
DEBU Container: ''
DEBU Image: 'fedora-toolbox:35'
DEBU Release: '35'
DEBU Resolved container name
DEBU Container: 'fedora-toolbox-35'
DEBU Resolving image name
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved image name
DEBU Image: 'fedora-toolbox:35'
DEBU Release: '35'
DEBU Resolving container name
DEBU Container: 'tools'
DEBU Image: 'fedora-toolbox:35'
DEBU Release: '35'
DEBU Resolved container name
DEBU Container: 'tools'
DEBU Checking if container tools exists
DEBU Inspecting mounts of container tools
DEBU Starting container tools
DEBU Inspecting entry point of container tools
DEBU Entry point PID is a float64
DEBU Entry point of container tools is toolbox (PID=0)
Error: invalid entry point PID of container tools
garrett
September 14, 2021, 3:04pm
#2
Toolbox works on Fedora 35, but it only works with Fedora 35 in the toolboxes. You can’t run other versions. It looks like it’s a glibc ABI thing.
Main bug is at:
opened 11:49AM - 30 Jun 21 UTC
closed 11:51PM - 21 Oct 21 UTC
1. Regression
2. Container Realm
Hello
I am using an Fedora Silverblur Rawhide 35 and after toolbox update to … version 0.0.99.2 I cannot start any container created before or after the upgrade, because of error: invalid entry point PID of container
I am attaching a logs with verbose:
```
[jakub@NBJSIERZEGA sbpwsdlvalidator]$ toolbox enter -vvv
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 jakub
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 /var/home/jakub/.config/toolbox
INFO[0000] podman filtering at log level debug
DEBU[0000] Called version.PersistentPreRunE(podman --log-level debug version --format json)
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /var/home/jakub/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/home/jakub/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /var/home/jakub/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /var/home/jakub/.local/share/containers/storage/volumes
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: mount_program=/usr/bin/fuse-overlayfs
DEBU[0000] backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=false
DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/crun"
INFO[0000] Found CNI network podman (type=bridge) at /var/home/jakub/.config/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
INFO[0000] Setting parallel job count to 25
DEBU[0000] Called version.PersistentPostRunE(podman --log-level debug version --format json)
DEBU Current Podman version is 3.3.0-dev
DEBU Creating runtime directory /run/user/1000/toolbox
DEBU Old Podman version is 3.3.0-dev
DEBU Migration not needed: Podman version 3.3.0-dev is unchanged
DEBU Resolving container and image names
DEBU Container: ''
DEBU Distribution: ''
DEBU Image: ''
DEBU Release: ''
DEBU Resolved container and image names
DEBU Container: 'fedora-toolbox-35'
DEBU Image: 'fedora-toolbox:35'
DEBU Release: '35'
DEBU Checking if container fedora-toolbox-35 exists
INFO[0000] podman filtering at log level debug
DEBU[0000] Called exists.PersistentPreRunE(podman --log-level debug container exists fedora-toolbox-35)
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /var/home/jakub/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/home/jakub/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /var/home/jakub/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /var/home/jakub/.local/share/containers/storage/volumes
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: mount_program=/usr/bin/fuse-overlayfs
DEBU[0000] backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=false
DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/crun"
INFO[0000] Found CNI network podman (type=bridge) at /var/home/jakub/.config/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
INFO[0000] Setting parallel job count to 25
DEBU[0000] Called exists.PersistentPostRunE(podman --log-level debug container exists fedora-toolbox-35)
DEBU Inspecting mounts of container fedora-toolbox-35
INFO[0000] podman filtering at log level debug
DEBU[0000] Called inspect.PersistentPreRunE(podman --log-level debug inspect --format json --type container fedora-toolbox-35)
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /var/home/jakub/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/home/jakub/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /var/home/jakub/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /var/home/jakub/.local/share/containers/storage/volumes
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: mount_program=/usr/bin/fuse-overlayfs
DEBU[0000] backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=false
DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/crun"
INFO[0000] Found CNI network podman (type=bridge) at /var/home/jakub/.config/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
INFO[0000] Setting parallel job count to 25
DEBU[0000] Called inspect.PersistentPostRunE(podman --log-level debug inspect --format json --type container fedora-toolbox-35)
DEBU Starting container fedora-toolbox-35
DEBU Inspecting entry point of container fedora-toolbox-35
INFO[0000] podman filtering at log level debug
DEBU[0000] Called inspect.PersistentPreRunE(podman --log-level debug inspect --format json --type container fedora-toolbox-35)
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /var/home/jakub/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/home/jakub/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /var/home/jakub/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /var/home/jakub/.local/share/containers/storage/volumes
DEBU[0000] overlay storage already configured with a mount-program
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: mount_program=/usr/bin/fuse-overlayfs
DEBU[0000] backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=false
DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/crun"
INFO[0000] Found CNI network podman (type=bridge) at /var/home/jakub/.config/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
INFO[0000] Setting parallel job count to 25
DEBU[0000] Called inspect.PersistentPostRunE(podman --log-level debug inspect --format json --type 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
```
Please help for resolving the issue.
A solution would be to statically compile the toolbox-init-container helper:
opened 05:47PM - 07 Jul 21 UTC
1. Feature request
**Is your feature request related to a problem? Please describe.**
This is an R… FE to solves issues such as https://github.com/containers/toolbox/issues/821 (comment https://github.com/containers/toolbox/issues/821#issuecomment-875616221) and add support for non-glibc toolboxes.
**Describe the solution you'd like**
Convert `toolbox-init-container` as a standalone static binary.
**Describe alternatives you've considered**
N/A
**Additional context**
This is required to avoid breaking toolbox every time the host is newer than the containers.
This is proposed as a blocker for Fedora 35 @https://bugzilla.redhat.com/show_bug.cgi?id=1995439
Meanwhile, if you’re going to run Fedora 35 beta, make sure to run Fedora 35 in toolbox (and make sure you have a recent version of the Fedora 35 toolbox image too, in case you pulled it a few days ago or more, as older versions were still set as rawhide and not F35).
You can make sure you have the latest Fedora 35 toolbox image by running:
podman pull registry.fedoraproject.org/fedora-toolbox:35
It’s a bit of a hassle, but they know about the issue and will hopefully be able to fix it soon.
Meanwhile, it seems there’s possibly a solution using a libc wrapper @ RFE: Make toolbox-init-container a fully static binary to avoid compatibility issues with container's glibc · Issue #832 · containers/toolbox · GitHub , so we might get the fix soon.
1 Like