I can create containers in toolbox but cannot enter them anymore.
I issued a "podman system reset", followed by "toolbox create" and "toolbox enter" but I still get "Error: failed to start container fedora-toolbox-40".
This is the first time trying to enter a container since upgrading from 39 to 40.
I have removed podman and toolbox and all their dependencies, and reinstalled them in case files/directories were missing but I'm still getting the same error.
It doesn't look to me like this is a "known" issue in that I can't seem to find references to this, and there doesn't appear to be a BZ for it. Not sure if it's random or a consequence of upgrading from 30 to 40.
zuke$ toolbox --verbose 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 Looking up sub-GID and sub-UID ranges for user admin DEBU TOOLBOX_PATH is /usr/bin/toolbox DEBU Migrating to newer Podman DEBU Toolbox config directory is /home/admin/.config/toolbox DEBU Current Podman version is 5.0.0 DEBU Creating runtime directory /run/user/1000/toolbox DEBU Old Podman version is 5.0.0 DEBU Migration not needed: Podman version 5.0.0 is unchanged DEBU Setting up configuration DEBU Setting up configuration: file /home/admin/.config/containers/toolbox.conf not found DEBU Resolving container and image names DEBU Container: '' DEBU Distribution (CLI): '' DEBU Image (CLI): '' DEBU Release (CLI): '' DEBU Resolved container and image names DEBU Container: 'fedora-toolbox-40' DEBU Image: 'fedora-toolbox:40' DEBU Release: '40' DEBU Resolving container and image names DEBU Container: '' DEBU Distribution (CLI): '' DEBU Image (CLI): '' DEBU Release (CLI): '' DEBU Resolved container and image names DEBU Container: 'fedora-toolbox-40' DEBU Image: 'fedora-toolbox:40' DEBU Release: '40' DEBU Checking if container fedora-toolbox-40 exists DEBU Inspecting mounts of container fedora-toolbox-40 DEBU Starting container fedora-toolbox-40 Error: failed to start container fedora-toolbox-40
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
Can you please report this for the test day here https://testdays.fedoraproject.org/events/181 and also file an issue at RHBZ under toolbox
On Wed, Mar 27, 2024 at 8:25 AM Ian Laurie nixuser@mail.com wrote:
I can create containers in toolbox but cannot enter them anymore.
I issued a "podman system reset", followed by "toolbox create" and "toolbox enter" but I still get "Error: failed to start container fedora-toolbox-40".
This is the first time trying to enter a container since upgrading from 39 to 40.
I have removed podman and toolbox and all their dependencies, and reinstalled them in case files/directories were missing but I'm still getting the same error.
It doesn't look to me like this is a "known" issue in that I can't seem to find references to this, and there doesn't appear to be a BZ for it. Not sure if it's random or a consequence of upgrading from 30 to 40.
zuke$ toolbox --verbose 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 Looking up sub-GID and sub-UID ranges for user admin DEBU TOOLBOX_PATH is /usr/bin/toolbox DEBU Migrating to newer Podman DEBU Toolbox config directory is /home/admin/.config/toolbox DEBU Current Podman version is 5.0.0 DEBU Creating runtime directory /run/user/1000/toolbox DEBU Old Podman version is 5.0.0 DEBU Migration not needed: Podman version 5.0.0 is unchanged DEBU Setting up configuration DEBU Setting up configuration: file /home/admin/.config/containers/toolbox.conf not found DEBU Resolving container and image names DEBU Container: '' DEBU Distribution (CLI): '' DEBU Image (CLI): '' DEBU Release (CLI): '' DEBU Resolved container and image names DEBU Container: 'fedora-toolbox-40' DEBU Image: 'fedora-toolbox:40' DEBU Release: '40' DEBU Resolving container and image names DEBU Container: '' DEBU Distribution (CLI): '' DEBU Image (CLI): '' DEBU Release (CLI): '' DEBU Resolved container and image names DEBU Container: 'fedora-toolbox-40' DEBU Image: 'fedora-toolbox:40' DEBU Release: '40' DEBU Checking if container fedora-toolbox-40 exists DEBU Inspecting mounts of container fedora-toolbox-40 DEBU Starting container fedora-toolbox-40 Error: failed to start container fedora-toolbox-40
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney -- _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hey Ian,
I have upgraded from F39 to F40 and followed the steps you did, I can't replicate this error. Here's my log https://paste.centos.org/view/61931a20
On Wed, Mar 27, 2024 at 8:36 AM Sumantro Mukherjee sumukher@redhat.com wrote:
Can you please report this for the test day here https://testdays.fedoraproject.org/events/181 and also file an issue at RHBZ under toolbox
On Wed, Mar 27, 2024 at 8:25 AM Ian Laurie nixuser@mail.com wrote:
I can create containers in toolbox but cannot enter them anymore.
I issued a "podman system reset", followed by "toolbox create" and "toolbox enter" but I still get "Error: failed to start container fedora-toolbox-40".
This is the first time trying to enter a container since upgrading from 39 to 40.
I have removed podman and toolbox and all their dependencies, and reinstalled them in case files/directories were missing but I'm still getting the same error.
It doesn't look to me like this is a "known" issue in that I can't seem to find references to this, and there doesn't appear to be a BZ for it. Not sure if it's random or a consequence of upgrading from 30 to 40.
zuke$ toolbox --verbose 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 Looking up sub-GID and sub-UID ranges for user admin DEBU TOOLBOX_PATH is /usr/bin/toolbox DEBU Migrating to newer Podman DEBU Toolbox config directory is /home/admin/.config/toolbox DEBU Current Podman version is 5.0.0 DEBU Creating runtime directory /run/user/1000/toolbox DEBU Old Podman version is 5.0.0 DEBU Migration not needed: Podman version 5.0.0 is unchanged DEBU Setting up configuration DEBU Setting up configuration: file /home/admin/.config/containers/toolbox.conf not found DEBU Resolving container and image names DEBU Container: '' DEBU Distribution (CLI): '' DEBU Image (CLI): '' DEBU Release (CLI): '' DEBU Resolved container and image names DEBU Container: 'fedora-toolbox-40' DEBU Image: 'fedora-toolbox:40' DEBU Release: '40' DEBU Resolving container and image names DEBU Container: '' DEBU Distribution (CLI): '' DEBU Image (CLI): '' DEBU Release (CLI): '' DEBU Resolved container and image names DEBU Container: 'fedora-toolbox-40' DEBU Image: 'fedora-toolbox:40' DEBU Release: '40' DEBU Checking if container fedora-toolbox-40 exists DEBU Inspecting mounts of container fedora-toolbox-40 DEBU Starting container fedora-toolbox-40 Error: failed to start container fedora-toolbox-40
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney -- _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED https://redhat.com/trusted
On 3/27/24 2:15 PM, Sumantro Mukherjee wrote:
Hey Ian,
I have upgraded from F39 to F40 and followed the steps you did, I can't replicate this error. Here's my log https://paste.centos.org/view/61931a20 https://paste.centos.org/view/61931a20
I have found the underlying problem.
"If a user is a member of any group that grants access to device nodes in folders that have 750 permissions, all toolboxes can no longer be entered."
Upstream bug:
https://github.com/containers/toolbox/issues/1348
I just removed myself from the vboxusers group and I can run toolbox and enter containers.
The consequences of this is that now I cannot pass USB devices to VirtualBox guests which is an epic pain, but I can live with it for now. Hopefully a fix comes soon.
I have added to the toolbox test day results and linked to the upstream bug from there.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
On 3/27/24 3:11 PM, Ian Laurie wrote:
Upstream bug:
Given that there is an upstream bug, and my toolbox test day results link to it, do you still want me to file a RHBZ as well?
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
On Wed, 2024-03-27 at 15:32 +1100, Ian Laurie wrote:
On 3/27/24 3:11 PM, Ian Laurie wrote:
Upstream bug:
Given that there is an upstream bug, and my toolbox test day results link to it, do you still want me to file a RHBZ as well?
It's not generally necessary, but if we wanted to get this fix into F40 Final and it did not land before Final freeze on Tuesday, it would need an FE bug.
On 3/28/24 2:32 AM, Adam Williamson wrote:
It's not generally necessary, but if we wanted to get this fix into F40 Final and it did not land before Final freeze on Tuesday, it would need an FE bug.
Despite 6 other bugs being classified as a duplicate of this one, the bug has not received a lot of attention since September 2023.
The original poster makes the point this breakage happens "in very common conditions".
It is frustrating when there are 3 proposed solutions, with one of them being standout one, that it hasn't progressed to a solution.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney