mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1008] Can't run Chromium in firejail with --overlay-tmpfs option #687
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#687
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @laniakea64 on GitHub (Dec 26, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1008
Xubuntu 16.04
firejail 0.9.44.2
Chromium version -
This works -
This, however, does not -
This also fails in firejail 0.9.38.
In Lubuntu 14.04, this still fails under firejail 0.9.44.2. But there it works fine in firejail 0.9.38.
How to get Chromium to run in firejail 0.9.44.2 with the
--overlay-tmpfsoption?@netblue30 commented on GitHub (Dec 27, 2016):
I'll put a fix in.
@netblue30 commented on GitHub (Jan 4, 2017):
All fixed in git.
@laniakea64 commented on GitHub (Jan 4, 2017):
Unfortunately can't try it out due to build failure -
@netblue30 commented on GitHub (Jan 4, 2017):
Fixed, problem in the Makefile.in.
@laniakea64 commented on GitHub (Jan 4, 2017):
Thanks!
In 14.04, Chromium now does run with
--overlay-tmpfs.Still fails in 16.04 though, same error as before. 🙁
@netblue30 commented on GitHub (Jan 4, 2017):
It's possible, I only tested it here on Debian stable. I'll give it a try on 16.04.
@netblue30 commented on GitHub (Feb 5, 2017):
Sorry I had to drop this, there are some security issues. For now, OverlayFS will require seccomp, and seccomp will prevent Chromium from starting.
@laniakea64 commented on GitHub (Feb 5, 2017):
Thank you for letting me know.
I tried building the latest firejail with the
--disable-seccompconfigure flag. And oddly, it didn't work there either.Anyway, I may have found a workaround -
Do I lose out on anything this way?
@netblue30 commented on GitHub (Feb 6, 2017):
You will still have seccomp enabled, it is just moved from chromium process to firejail process.
It is very difficult to say what is the best place for seccomp to be. In both cases there are advantages and disadvantages.