You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes - when running devpod with a docker-compatible executable (such as podman) using SELinux, the container gets permission denied on the mounted workspace folder
Which solution do you suggest?
It looks like adding the Z flag is enough to make it work:
As you mentioned adding the Z is needed to allow the runtime to mount the volume. We opted to not automatically add this as we would need to detect SELinux and add the flag which is potentially not desired behaviour for other users.
Let me know if you have any specific ideas though about this or how it could be supported
which is potentially not desired behaviour for other users.
Yes that makes sense. Could we consider adding an option similar to SSH_ADD_PRIVATE_KEYS to be used in tandem with DockerHelper.SELinuxEnabled? The rational being, devpod offers the great feature of working directly off a git repo, but the workaround require changing the devcontainer spec prior to running it.
As I mentioned in the initial report, in case this is something you would be okay to see in devpod, I'd be happy to submit my contribution!
Hi @acolombier yes that would work! As long as we can toggle this functionality with a CLI flag then it would be great if you could submit a PR with your changes :) I think adding --disable-selinux-flag to the up command would suffice.
Is your feature request related to a problem?
Yes - when running devpod with a docker-compatible executable (such as
podman
) using SELinux, the container gets permission denied on the mounted workspace folderWhich solution do you suggest?
It looks like adding the
Z
flag is enough to make it work:Let me know if you would like me to submit a PR
Which alternative solutions exist?
N/A
Additional context
Using the
main
version of devpod, using withpodman
on Fedore 41 SilverBlueThe text was updated successfully, but these errors were encountered: