-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Incompatable with SELinux #73
Comments
@PolyPoyo Is it possible that your docker requires root? |
No, it works just fine when in Permissive mode |
Ok, |
I also suggest upgrading to latest. |
I have the same problem on Fedora 41
I grabbed the latest version from the release page. |
From SELinux:
|
Interesting. Not sure if this is caused by the packaged executable either. I’ll probably need someone with Fedora or SELinux to debug the issue. In general there are very few linux users and that’s probably why this wasn’t caught for a very long time. I wonder if that z flag applies to Fedora or not… For a bit of a lead here: the most straightforward strategy is making the tool exit just after it fails and manually execute the docker command to replicate & search for a solution. |
The problem is the way that it mounts the /libdragon volume
needs to be (capital Z)
I'm not exactly sure where this /libdragon mount is declared though, I don't see it in the |
libdragon-docker/modules/actions/start.js Line 37 in 84e0c06
—mount though.
|
For example I can see right now it does this:
According to Docker: "It is not possible to modify the SELinux label using the --mount flag." So it would need to be:
|
Looks like a permanent change on filesystem (from docker docs) and I honestly don’t know what are “label”s in the context of SELinux. edit: I think this is the relevant feature |
I think we will need explicit approval from the user to add that label. It can be an SELinux specific config flag that you need to initially provide to lock the project to a given host path. But then it is not transferable to another system. I think providing the path manually as a flag on every |
Yes it is a change to the filesystem, if you are worried about making these changes via the program, you could add some documentation like this:
This is what I need to do to get it to work on my system. |
Adding documentation is also a good middle ground as this is rather technical so I don’t expect an average user needing support for SELinux. Docker user id is set to your actual user id so world-writable shouldn’t be necessary. At which point do you get an error wheb you don’t do that? Maybe there is something different with how SELinus handles users. |
oh haha true, I realize that I am UID 1000. This may be a Podman thing, I am using Podman rather than Docker. I notice that the files are created by UID 525287, which is probably a random UID generated by Podman |
On second thought, it should be the uid running the cli so I can’t think a way podman can change things 🤔 |
When running
libdragon init
on Fedora Server 39, it fails with the following error:SELinux Logs during
libdragon init
The text was updated successfully, but these errors were encountered: