-
Notifications
You must be signed in to change notification settings - Fork 52
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
Option to start virtiofsd
with namespacing/uid-map enabled
#202
Comments
Hello, Interesting use-case!
Maybe there is a way to detect when these options are needed? Or adding a new option to both |
Cheers :)
Yeah, I am using mkosi to generate my rootfs which generally does everything as the user and am toying around with virtme-ng for some CI stuff
mkosi also allows booting the image and they check if the invoking uid+gid equals the uid+gid of the root of the filesystem and depending on that invoke unshare the namespace: |
If there is a way to detect when virtme-ng/virtme/commands/run.py Lines 681 to 684 in ba08268
Because you have the environment, and I see you successfully contributed to |
I have a prebuild rootfs where all files are owned by my user instead of root. Using that as the root for virtme results in errors as apparently
mount -t tmpfs run /run
fails in those cases. It would be great if there was an option to enable the--sandbox
or--uid-map
flags for thevirtiofsd
invocation. My current workaround is to rununshare --map-root-user virtme-run ...
but I am not sure if there are other side effectsThe text was updated successfully, but these errors were encountered: