F32 (recently branched) toolbox container still uses rawhide repos as default #381
Comments
|
https://github.com/containers/toolbox/blob/master/images/fedora/f32/Dockerfile actually looks reasonable. I first checked the fedora:32 container image, and it also seems okay:
The container still has /etc/yum.repos.d/fedora-rawhide.repo , but it's disabled by default. The problem is that the toolbox f32 container is out of date:
That image was created 3 months (!) ago, waay before F32 branched off. So it seems that toolbox F32 image simply needs to be rebuilt, then everything should be fine. |
|
BTW, registry.fedoraproject.org/f31/fedora-toolbox was built 5 months ago -- any chance that could get a refresher too, so that after creation one doesn't need to spend so much time installing upgrades? |
|
@juhp, could you, please, rebuild the image? |
|
I was trying to build them last week but they failed - will try again. |
|
I dunno why but dnf is still giving a 143 error: https://koji.fedoraproject.org/koji/taskinfo?taskID=41976528 (f33) Same for f32 container (f31 builds okay). (There is also the Fedora Container Images product in bugzilla with fedora-toolbox component, but to be honest I find it just as easy to track here.) |
|
Even after that (ie skipping missing-docs), I see install errors:
|
|
Seems cap_set_file error is caused by containers/buildah#2176 (ie buildah-1.14.0). |
|
Yep, thanks for testing (and spotting the new images - I had meant to report back here:) |
Note: This is not about toolbox the toolbox command itself, but about the F32 container that toolbox uses.
Apologies in advance if this is not the right place to report the issue. (If not here, where is the correct place? Bugzilla... or here... or somewhere else?)
After upgrading to Fedora 32 pre-beta using Silverblue, creating a toolbox container works (thankfully), but a Fedora 32 container still uses rawhide in
/etc/yum.repos.d/*. (Rawhide repos are enabled and normal, non-rawhide Fedora repos are not enabled.)DNF installs and upgrades then fail with a mismatched key.
(Truncated verbose output with ellipses, to show relevant parts.)
The text was updated successfully, but these errors were encountered: