-
Notifications
You must be signed in to change notification settings - Fork 199
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
unable to build tree in docker container in fedora 31 #1943
Comments
if i set selinux: false in treefile, this error not happens |
but happened another one
|
after doing rpm-ostree usroverlay and install docker-ce, i can build my tree again (without unified-core). |
@vtolstov I had the same problem and managed to fix it with the following arguments to
Where You might have to remove the cache directory before trying again. |
The most frictionless way to run rpm-ostree in a container is via coreos-assembler. It's shipped as a container and is fully supported in rootless mode (but requires But of course, running rpm-ostree directly is also still supported. It works fine for me in a podman container with |
Hey there, I want to add my experiences here. I'm using F31 - F33 in my setup and it's a bit wild so please bare with me :) It might be worth to open another issue on this, but I want to relate first since I'm seeing the same error messages. My current situation is that I have a F33 based rpm-ostree container that reports I have another container, based on F32, which is running in a CI pipeline on a CentOS 7 host (also --privileged) that executes rpm-ostree builds just fine. This exact same container throws I've then tested the F33-based rpm-ostree container on a CentOS 7 host (like the one working based on F32) and it fails there with SELinux errors as well. I'm using SELinux, so turning it off is not an option. I'm using rpm-ostree with --unified-core if that makes a difference. I then also have a EC2 autoscaler running the working F32 based container. On EC2 the F32 container also failed at first, while I was still using a standard ubuntu AMI. After switching over to an CentOS 7 AMI it worked. So to warp it up, I'm currently having a F33 based rpm-ostree container with no extra dependencies installed that does not work on a CentOS 7 host, nor F33 Workstation. I'm really confused and I don't really understand what's happening here. Of course I'll investigate this further, but maybe someone else can relate or even give a hint or something. Well, it's just a hell of different variables to test and compare here. I'll come back later with a more "structured" write up on this, after a bit more testing. EDIT: OK nvm.! The missing piece here was that I'm building against fedora-33 repos, but in the failing case didn't use fedora-33-updates which caused the error |
I'm hitting this on the Silverblue F36 beta trying to update Zoom to the newest release:
This is on the host workstation, not within any toolbox or container. |
@heyakyra This seems like a distinct issue. Can you file a separate ticket? Please include where you got the RPM, and the version of rpm-ostree (and |
Foolishly, this seems to be the result of me purging Any help recovering from this much appreciated! |
after successful deploy fedora 31 from builded ostree repo (host fedora 29, container fedora 31)
now i can't build the same tree under fedora 31 host system (host fedora 31, container fedora 31)
before downloading packages i have some messages like
and it always stuck at Installing packages, percentage varies from 17 to 43 from one build to another. it can't be stopped by hitting ctrl+c.
I'm try to add unified core options, but it fails with:
The text was updated successfully, but these errors were encountered: