Toolbox fails to start on Fedora 35

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

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:
https://github.com/containers/toolbox/issues/821

A solution would be to statically compile the toolbox-init-container helper:
https://github.com/containers/toolbox/issues/832

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 or disable CGO to avoid compatibility issues with container's glibc · Issue #832 · containers/toolbox · GitHub, so we might get the fix soon.

1 Like