Closed baldemoto closed 1 month ago
Update: After a few reinstalls of Silverblue, I have narrowed down the potential cause of the issue.
My suspicion is there might be a conflict within some hidden directory in the /home folders or within home directory permissions themselves. I will investigate further later.
Looks like toolbox just eats up all stderr from the start command and never logs the actual podman error so you likely want to fix this first. https://github.com/containers/toolbox/blob/b684b190d1d931434d0d7d63c841973101dfb928/src/cmd/run.go#L976-L984
Podman stores all the images, containers,etc... under ~/.local/share/containers/
and yes moving this to another computer will not work if your UID is changed, /etc/sub{u,g}id were changed or in general some paths where changed that now trip over over our db validation code.
A friendly reminder that this issue had no activity for 30 days.
Issue Description
After creating a toolbox container (
toolbox create env
), attempting to enter it withtoolbox enter env
fails.Steps to reproduce the issue
Fedora Linux 40.20240828.0 (Silverblue)
podman system reset
toolbox create testenv
)toolbox enter testenv
Describe the results you received
I expected toolbox to start without any further issues.
Describe the results you expected
After downloading the Fedora 40 image
registry.fedoraproject.org/fedora-toolbox:40
and creating the container, I receive the following error after attempting to enter the environment:Error: failed to start container testenv
Further debug information is attached below
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
This is a fresh install of Fedora Silverblue. The actions I have performed include:
chmod 770
)nordvpn-3.18.4-1.x86_64
, rpmfusion free and nonfree packages ,mesa-va-drivers-freeworld-24.1.6-1.fc40.x86_64
, Cosmic DE)This is a very similar issue to #13807 , though that one was seemingly resolved on its own.
Additionally, running
podman start --attach testenv
outputs the following error:The following is the output of
toolbox enver -vvvv testenv
: