-
Notifications
You must be signed in to change notification settings - Fork 569
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
Virtualbox not able to write to /dev/vbox* #2868
Comments
Thanks for reporting this @Niklas974 ! Besides the error messages, does this cause any issues with virtualbox? If it's just error messages then it's probably better to say these are just cosmetic issues and not change/remove Thanks! |
NOTE: I edited the original report, it is not "netfilter" but "caps.drop all" that causes the problem! Hi @Fred-Barclay , thank you for helping with this issue! Using the original config file provided by firejail, VirtualBox does work, at least the following do not work: (see hints on Virtualbox Networking here) |
@Niklas974 |
(From outside of firejail) |
Same with |
|
Well, no idea more how to findout what we need for |
AFAIK vbox uses full suid binaries instead of caps. @Niklas974 could you show Also could you try replacing Alternatively |
@Vincent43
|
So, this one looks sufficient. @Niklas974 |
I have just tried |
Ok, we go for |
with this profile i still cannot change the IPv4 address for adapter and DHCP server when adding a Host-only network. I already created an exception like described in this manual section: cat /etc/vbox/networks.conf and now it works when called dircetly via But with firejail i still get this error message:
|
@githlp The virtualbox profile has |
that did not work, the error message remains the same. |
I noticed the original fix from d94e38a got changed later on. Did you see the comment about needing |
Yes, I followed the comment within virtualbox.profile and added sys_admin to the caps.keep line. I just checked again and both is fullfilled: /etc/firejail/virtualbox.profile ~/.config/firejail/virtualbox.local |
@githlp Good. In that case you have some detective work to do. Adding |
well with this setting in virtualbox.local the host-based network adapter can be set up/modified
but does it make sense to ignore the caps.keep completely ? i still get those messages in journal every time i start virtualbox
and this is the output on the shell |
The network does not get a connection on the default route 10.0.2.15, too. Started without firejail it works on same config settings. |
@githlp Apologies for the radio-silence. The pastebin has expired but here's what I see in my notes:
|
but still no connection on my 10.0.2.x virtual eth
|
I'm using firejail version 0.9.58.2 and VirtualBox Version 6.06 on Ubuntu 19.04
Running virtualbox in firejail using the default virtualbox profile provided by firejail, I run into networking issues when accessing host-only network adapters in the virtualbox "host-only network manager"
(translated: The Host-Network Interface could not be created)
interestingly, /dev/vbox* looks pretty similar from the outside and from inside the virtualbox firejail:
commenting out "caps.drop all" in the virtualbox profile solves the issue locally
I think this should be fixed or at least annotated in the virtualbox profile.
I know that I do not run the latest version of firejail, but the one provided by ubuntu. If you need me to try with the newest version, please let me know.
EDIT: I previously claimed that commenting out "netfilter" would provide a work-around. It turns out that the "caps.drop all" line is the culprit.
Hint for debugging: On closing the virtualbox GUI, it takes a few seconds for the last virtualbox process to end, if you do not wait for them to end, firejail will not reload the config and thus ignore potential changes.
The text was updated successfully, but these errors were encountered: