Breaks existing toolboxes, but that's acceptable at least to me -- containers are not supposed to live forever. Creating a new F34 and Debian unstable toolbox works fine at last, so I could now upgrade to Fedora 35 at last. Thank you!
BZ#1995439 /usr/bin/toolbox linked against glibc-2.34 doesn't run on older glibc
Mmm... I think all (even old) toolbox containers have /run/host inside of them. I think the real problem that there is no /run/host/lib64 in those containers as that started to be done not that long ago (as part of mounting the whole root filesystem of the host into /run/host). I also have such a container around.
This update has been submitted for testing by rishi.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
This update's test gating status has been changed to 'passed'.
The bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1995439#c13 haven't error
This update can be pushed to stable now if the maintainer wishes
On Fedora 35:
$ sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ec38b7db52
$ toolbox create 34 -r 34 Creating container 34: | Created container: 34 Enter with: toolbox enter 34
$ toolbox run -c 34 grep PRETTY /etc/os-release PRETTY_NAME="Fedora 34 (Container Image)"
It works here; thanks for the fix!
This update has been submitted for stable by bodhi.
This change breaks all the old Toolbox containers, even F-35 containers. I don't think it is a good solution.
Breaks existing toolboxes, but that's acceptable at least to me -- containers are not supposed to live forever. Creating a new F34 and Debian unstable toolbox works fine at last, so I could now upgrade to Fedora 35 at last. Thank you!
@cheeselee, could you provide some logs from the breakage of the containers? My impression was that the fix should work even with existing containers.
Old containers do not have /run/host mapped. So the toolbox executable fail to run inside container.
Mmm... I think all (even old) toolbox containers have
/run/hostinside of them. I think the real problem that there is no/run/host/lib64in those containers as that started to be done not that long ago (as part of mounting the whole root filesystem of the host into/run/host). I also have such a container around.Oops, sorry about that. I submitted a new pull request to restore backwards compatibility with older containers: https://github.com/containers/toolbox/pull/904
This update has been unpushed.
adamwill edited this update.
This update has been submitted for testing by adamwill.
I unpushed this to ensure it doesn't get pushed "over the top" of the -4 we just pushed stable.