This seems to break toolbox. Creating a new toolbox works fine (toolbox create), but rebooting and trying to start an existing one (toolbox enter) fails. I'll create a bz with more information shortly.
But after podman stop test (or rebooting the machine, which is the usual way how to get here):
toolbox --verbose enter -c test
toolbox: running as real user ID 1000
toolbox: resolved absolute path for /bin/toolbox to /usr/bin/toolbox
toolbox: checking if /etc/subgid and /etc/subuid have entries for user martin
toolbox: TOOLBOX_PATH is /usr/bin/toolbox
toolbox: running on a cgroups v2 host
toolbox: current Podman version is 1.6.2
toolbox: migration not needed: Podman version 1.6.2 is unchanged
toolbox: Fedora generational core is f31
toolbox: base image is fedora-toolbox:31
toolbox: container is test
toolbox: checking if container test exists
toolbox: calling org.freedesktop.Flatpak.SessionHelper.RequestSession
toolbox: starting container test
toolbox: /etc/profile.d/toolbox.sh already mounted in container test
Error: unable to start container "test": container create failed (no logs from conmon): EOF
toolbox: failed to start container test
Do you see something like the following in your journal?
Failed to mkfifo at ~/.local/share/containers/storage/overlay-containers/a26bc82e68ec049d2c8857ec6c916f3873cd8ebe7635e0fb4bd07b3ef4c6596a/userdata/winsz: File exists
@gscrivano: sudo journalctl --since '2 days ago' | grep mkfifo has no hits, and I didn't see that error message anywhere. I'll test with the previous version in a bit, with ostree that's not entirely trivial.
crun doesn't keep any persistent data (everything is stored under $XDG_RUNTIME_DIR) so I think it was just an issue in the interaction Podman-conmon, fixed with the new Podman
This update's test gating status has been changed to 'greenwave_failed'.
This update has been submitted for testing by gscrivano.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'greenwave_failed'.
This update's test gating status has been changed to 'ignored'.
FEDORA-2019-743e6dffa1 ejected from the push because "Cannot find relevant tag for crun-0.11-1.fc31. None of ['f31-updates-testing', 'f31-updates-testing-pending'] are in ['dist-6E-epel-testing-candidate', 'epel7-testing-candidate', 'dist-5E-epel-testing-candidate', 'f27-modular-updates-candidate', 'f30-modular-updates-candidate', 'f30-container-updates-candidate', 'f30-flatpak-updates-candidate', 'f28-modular-updates-candidate', 'f28-container-updates-candidate', 'epel8-testing-candidate', 'f31-modular-updates-candidate', 'f32-container-updates-candidate', 'f31-container-updates-candidate', 'f31-flatpak-updates-candidate', 'f29-modular-updates-candidate', 'f29-container-updates-candidate', 'f29-flatpak-updates-candidate', 'f22-updates-candidate', 'f21-updates-candidate', 'f25-updates-candidate', 'f24-updates-candidate', 'f23-updates-candidate', 'f26-updates-candidate', 'f27-updates-candidate', 'f30-updates-candidate', 'f28-updates-candidate', 'f31-updates-candidate', 'f32-updates-candidate', 'f29-updates-candidate', 'el8-modular-updates-candidate']."
This update has been pushed to testing.
Podman seems to work fine, +1
This seems to break toolbox. Creating a new toolbox works fine (toolbox create), but rebooting and trying to start an existing one (toolbox enter) fails. I'll create a bz with more information shortly.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
thanks for the feedback. What error message are you seeing?
New creation works:
But after
podman stop test(or rebooting the machine, which is the usual way how to get here):Slightly more info when trying to start the test container directly with podman:
I think that is a podman issue rather than crun:
Do you see something like the following in your journal?
Failed to mkfifo at ~/.local/share/containers/storage/overlay-containers/a26bc82e68ec049d2c8857ec6c916f3873cd8ebe7635e0fb4bd07b3ef4c6596a/userdata/winsz: File exists
could you confirm it is working correctly with the previous version?
@gscrivano:
sudo journalctl --since '2 days ago' | grep mkfifohas no hits, and I didn't see that error message anywhere. I'll test with the previous version in a bit, with ostree that's not entirely trivial.I just upgraded my system again, which pulled in a new kernel and a new podman, and now it works again.
toolbox-0.0.17-1.fc31.noarch podman-1.7.0-2.fc31.x86_64 crun-0.11-1.fc31.x86_64 kernel-5.4.8-200.fc31.x86_64
So apparently this new crun needs the new podman?
This update can be pushed to stable now if the maintainer wishes
crun doesn't keep any persistent data (everything is stored under $XDG_RUNTIME_DIR) so I think it was just an issue in the interaction Podman-conmon, fixed with the new Podman
This update's test gating status has been changed to 'greenwave_failed'.
This update's test gating status has been changed to 'ignored'.
This update has been obsoleted by crun-0.12-1.fc31.