-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid entrypoint on later versions of Toolbox #871
Comments
See #821 |
After some time not being able to update fedora-toolbox images due to a fedora buil infrastructure bug, @debarshiray and @juhp were able to update the images for f35 and f36 (rawhide). Please, update the images as the glibc versions should match now. |
Well, this still affects any non-Fedora toolbox using older glibc |
Yup, some containers stopped working for me for that reason. I don't want to install |
I have been seeing this for quite a while too. Can we add |
So I tried this for fun actually: patched toolbox to not mount /usr/bin/toolbox into the toolbox container A gentle approach would be to not bind mount the host toolbox binary into the container if the file already exists. |
This is unfortunate, and will keep me away from f35. |
Duplicate of #821 |
Describe the bug
A clear and concise description of what the bug is. If possible, re-run the command(s) with
--log-level debug
and put the output here.One of my Toolbox containers worked in Fedora 34 Silverblue, but it stopped working in Fedora 35 Silverblue.
Steps how to reproduce the behaviour
toolbox create --image registry.gitlab.com/theevilskeleton/jekyll-toolbox
jekyll-toolbox
containerExpected behaviour
Commands should run as intended.
Actual behaviour
Gives the following error:
Output of
toolbox --version
(v0.0.90+)toolbox version 0.0.99.2
Toolbox package info (
rpm -q toolbox
)toolbox-0.0.99.2^3.git075b9a8d2779-1.fc35.x86_64
Output of
podman version
Podman package info (
rpm -q podman
)podman-3.3.0-1.fc35.x86_64
Info about your OS
Fedora Silverblue 35
Additional context
As explained before, this issue happened after I upgraded to Fedora Silverblue 35.
If you see an error message saying:
Error: invalid entry point PID of container <name-of-container>
, add to the ticket output of commandpodman start --attach <name-of-container>
.The text was updated successfully, but these errors were encountered: