Can't get toolbox working in Fedora Silverblue Beta 31

Project Discussion
#1

Hi all,

I rebased from SB30 to SB31 Beta but I can’t get toolbox to work correctly…
I am getting this:

[gordy@silverblue ~]$ toolbox -v enter

toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox
toolbox: checking if /etc/subgid and /etc/subuid have entries for user gordy
toolbox: TOOLBOX_PATH is /usr/bin/toolbox
toolbox: checking if ‘podman system migrate’ exists
toolbox: migration not needed: 1.5.1 is unchanged
toolbox: Fedora generational core is f31
toolbox: base image is fedora-toolbox:31
toolbox: container is fedora-toolbox-31
toolbox: checking if container fedora-toolbox-31 exists
toolbox: calling org.freedesktop.Flatpak.SessionHelper.RequestSession
toolbox: starting container fedora-toolbox-31
toolbox: /etc/profile.d/toolbox.sh already mounted in container fedora-toolbox-31
Error: unable to start container “fedora-toolbox-31”: error reading container (probably exited) json message: EOF
toolbox: failed to start container fedora-toolbox-31

Anyone got any workarounds or solutions to this?
Thanks in advance,

Gordy

#2

Hi @bakerboy26,

This is due to one or more underlying bugs in Podman the fix is below.

Verify that ~/.config/containers/storage.conf is not using a camel-case format. If it is, then replace it with the lower-case example in containers/libpod#2158. Then sudo rm -rf ~/.local/share/containers and try again. However, you’d lose all existing containers and images.

Otherwise, I would recommend rolling back to Fedora SB 30 until the Final release of Fedora SB 31

rpm-ostree rollback

Kinoite, a KDE (and now XFCE) version of Fedora Silverblue
#3

Apparently it’s a bit more complicated, not sure where to report it:

Error: unable to start container "fedora-toolbox-31": time="2019-09-22T00:11:14+02:00" level=warning msg="signal: killed"
time="2019-09-22T00:11:14+02:00" level=warning msg="no such directory for freezer.state"
time="2019-09-22T00:11:14+02:00" level=warning msg="no such directory for freezer.state"
time="2019-09-22T00:11:14+02:00" level=error msg="container_linux.go:346: starting container process caused \"process_linux.go:297: applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n"
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for cgroup not found\"": OCI runtime error

full log: https://pastebin.com/LVkbuY7c
build-devbox.sh removes old toolbox containers, starts a new one and installs stuff in it. Based on something found around the forums.

#4

I am getting this as well and miker256’s fix didn’t work on my end.

#5

I am another troubled soul with this issue. There was talk about unset NOTIFY_SOCKET being a solution but it was not the case for me.

#6

I am currently running toolbox on Silverblue 31. Besides what @miker256 says you will need to override podman with
podman 1.6.0-0.18.dev.git6ce8d05.fc32.x86_64 or later (from Koji) and make sure you have installed the latestgnome-shell-3.34.0-3.fc31 and latest gnome-session-3.34.0-3.fc31. Not on my computer at the moment but that should be what is needed.

Toolbox should run fine afterwards but beware, if you stop (for whatever reason) the toolbox container with podman stop, you won’t be able to re enter the container until you reboot the system (I have not worked out yet what files need to be manually cleared to re enter the container without rebooting)

#7

I can confirm what issue is still present in Fedora Silverblue 31 (fresh installation, build 31.20191001.n.0, basecommit f343f95c7a94865c6d490b11286f99e3e47bad3aa7bcb254d3f3451ea705157e).

First I’ve got the same error as a TS:
toolbox: /etc/profile.d/toolbox.sh already mounted in container fedora-toolbox-31
Error: unable to start container “fedora-toolbox-31”: error reading container (probably exited) json message: EOF

When I’ve checked the config format and removed ~/.local/share/containers. Nothing changed…

Looks like it’s broken until podman will be updated in Fedora 31

#8

Overriding podman with a new version don’t work too. :frowning:

$ toolbox -v enter
toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox
toolbox: checking if /etc/subgid and /etc/subuid have entries for user ezakharov
toolbox: TOOLBOX_PATH is /usr/bin/toolbox
toolbox: checking if 'podman system migrate' exists
toolbox: migration not needed: 1.6.1 is unchanged
toolbox: Fedora generational core is f31
toolbox: base image is fedora-toolbox:31
toolbox: container is fedora-toolbox-31
toolbox: checking if container fedora-toolbox-31 exists
toolbox: calling org.freedesktop.Flatpak.SessionHelper.RequestSession
toolbox: starting container fedora-toolbox-31
toolbox: /etc/profile.d/toolbox.sh already mounted in container fedora-toolbox-31
Error: unable to start container "fedora-toolbox-31": remount '/var/home/ezakharov/.local/share/containers/storage/overlay/32a3ae5e69eb32586fadac20735f2ec53b980f86eeaa148fb8f83f5fe24e079a/merged/run/host/usr': Operation not permitted: OCI runtime permission denied error
toolbox: failed to start container fedora-toolbox-31

Used these builds to override:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1393621
https://koji.fedoraproject.org/koji/buildinfo?buildID=1393143

#9

I overlayed podman with the version you specified and I’ve got a working toolbox on F31.

1 Like
#10

Lattest podman from updates-testing is working, no luck yet with toolbox.

#11

I had issues with docker and cgroup, can this be related to the same issue? https://fedoraproject.org/wiki/Changes/CGroupsV2#Scope

#12

Yes, but at least in the testing branch those (toolbox and podman errors) should be fixed. I don’t know about docker but that should be easiert to fix than podman.

#13

Any updates as to whether this was resolved?

#14

The toolbox is working for me. I have installed Silverblue 31 Beta 3 days ago.

1 Like
#15

Yes, this is fixed in fedora 31 (even without the updates-testing repo). If it is not working for someone, purging the configs (~/.config) for podman and toolbox and the files in ~/.local/share/containers should fix this.

#16

Thanks all! Just upgraded and this appears fixed!

#17

cool get a rebase done at some point this weekend now :slight_smile:

#18

So rebase to to 31, try and enter toolbox and get
toolbox: unable to migrate containers: Podman version couldn’t be read

@deathwish

If it is not working for someone, purging the configs ( ~/.config ) for podman and toolbox and the files in ~/.local/share/containers should fix this.

What files is it I should delete / purge? Is it the ones in the ~/.config/containers/ and everything in the ~/.local/share/containers folders?

#19

Everything. But you will lose all your containers.

#20

Hmmmm. I’m looking for a ‘fix’ that will not require me to nuke my current containers and custom toolboxes. I have stuff that runs python2, other gnome apps, other tools with network stuff. Yeah with some effort I can recreate all that, but I’m also on a slow expensive internet connection, so this is going to be hours and $$. A more stable upgrade would be preferable. If anyone has any further suggestions…???