Skip to content
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

Closed
TheEvilSkeleton opened this issue Sep 9, 2021 · 8 comments
Closed

Invalid entrypoint on later versions of Toolbox #871

TheEvilSkeleton opened this issue Sep 9, 2021 · 8 comments
Labels
1. Bug Something isn't working

Comments

@TheEvilSkeleton
Copy link

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

  1. run toolbox create --image registry.gitlab.com/theevilskeleton/jekyll-toolbox
  2. Run any command inside the jekyll-toolbox container

Expected behaviour
Commands should run as intended.

Actual behaviour
Gives the following error:

Error: invalid entry point PID of container jekyll-toolbox

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

Version:      3.3.0
API Version:  3.3.0
Go Version:   go1.16.6
Built:        Fri Aug 20 15:35:44 2021
OS/Arch:      linux/amd64

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 command podman start --attach <name-of-container>.

❯ podman start --attach jekyll-toolbox 
toolbox: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by toolbox)
@TheEvilSkeleton TheEvilSkeleton added the 1. Bug Something isn't working label Sep 9, 2021
@vchernin
Copy link

vchernin commented Sep 9, 2021

See #821

@olivergs
Copy link
Collaborator

olivergs commented Sep 9, 2021

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.

@nanonyme
Copy link
Contributor

nanonyme commented Sep 9, 2021

Well, this still affects any non-Fedora toolbox using older glibc

@TheEvilSkeleton
Copy link
Author

TheEvilSkeleton commented Sep 9, 2021

Yup, some containers stopped working for me for that reason. I don't want to install GLIBC_2.34 on every container, especially on those that don't have a package manager like the container I use to be honest.

@juhp
Copy link
Contributor

juhp commented Sep 10, 2021

I have been seeing this for quite a while too.

Can we add toolbox to fedora-toolbox??

@juhp
Copy link
Contributor

juhp commented Sep 11, 2021

Can we add toolbox to fedora-toolbox??

So I tried this for fun actually: patched toolbox to not mount /usr/bin/toolbox into the toolbox container
and created a localhost/fedora-toolbox:34 with toolbox preinstalled and it starts fine on F35!

A gentle approach would be to not bind mount the host toolbox binary into the container if the file already exists.

@matthiasclasen
Copy link
Collaborator

This is unfortunate, and will keep me away from f35.

@debarshiray
Copy link
Member

Duplicate of #821

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants