[GH-ISSUE #1556] Running Virtualbox with seccomp? #1035

Closed
opened 2026-05-05 07:20:02 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @Futureknows on GitHub (Sep 17, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1556

Is it possible to firejail Virtualbox with seccomp or namespace?

Originally created by @Futureknows on GitHub (Sep 17, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1556 Is it possible to firejail Virtualbox with seccomp or namespace?
gitea-mirror 2026-05-05 07:20:02 -06:00
Author
Owner

@netblue30 commented on GitHub (Sep 18, 2017):

Virtualbox needs to raise privileges in order to start or communicate with its own kernel modules. Seccomp will kill it immediately. Namespaces are working fine and are currently enabled. Also, the home directory is whitelisted, so you have access only to ~/VirtualBox and ~/Downloads directory.

<!-- gh-comment-id:330206833 --> @netblue30 commented on GitHub (Sep 18, 2017): Virtualbox needs to raise privileges in order to start or communicate with its own kernel modules. Seccomp will kill it immediately. Namespaces are working fine and are currently enabled. Also, the home directory is whitelisted, so you have access only to ~/VirtualBox and ~/Downloads directory.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1035
No description provided.