-
-
Notifications
You must be signed in to change notification settings - Fork 8k
[Installation]: Can't build arm container image with podman without a SELinux relabel of bind mounts #12734
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
Comments
You can do podman build --security-opt label=disable ... What AVC's are you seeing. I have a feeling is is something to do with one of the cache our mount types. sudo ausearch -m avc |
Dumping the AVC's from today below:
|
Only one of those has anything about containers, but you could probably fix most of them via sudo restorecon -R -v /etc On the host. |
The AVC I am seeing looks like you Containerfile should have fixed it. Could you try this again in enforcing mode and then send me the AVC's again. BTW you could also do sudo cat /dev/null > /var/log/audit/audit.log |
Those AVCs did come from a SELinux enforcing podman machine. I created a new machine and ran the failing build: The new AVC that popped up after attempting a build with the Dockerfile.arm is:
Total AVC dump:
/dev/null output was:
Running podman build with --security-opt label=disable did also let the image build on Dockerfile.arm! |
did the trick for me as well below is my
|
ARM images aren't published in Docker Hub -> https://hub.docker.com/r/vllm/vllm-openai/tags is it possible to get them also uploaded there? |
Your current environment
The error from building the arm Dockerfile using the Apple silicon CPU docs:
Workaround is to use a Containerfile.arm that mirrors Dockerfile.arm except for adding a
relabel=private
to each bind mount to ensure compatability with SELinux:Containerfile.arm
And this builds:
I can submit a PR to add that Containerfile, but that may not be the best long term solution so open to any thoughts!
How you are installing vllm
Before submitting a new issue...
The text was updated successfully, but these errors were encountered: