mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2036] Can't combine --overlay-named with --private= #1372
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#1372
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 @laenion on GitHub (Jul 11, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2036
My intention is to install an application into an overlay (to keep it separate from the regular system). Both the system and home directories should be persistent, however the application should not see my personal data and start with an empty home.
The idea was to do this with the following command line:
firejail --private-home="/path/to/application/home" --overlay-named="Application name"While the overlay is created as expected the original contents of my user's home are still visible.
Probably related to #1743.
Firejail version: 0.9.52 & today's master
Distribution: openSUSE Leap 15
@chiraag-nataraj commented on GitHub (Jul 11, 2018):
I get this warning when I use them together:
(using master)
So it seems that this is a known issue. I'll add an enhancement tag to it.
@chiraag-nataraj commented on GitHub (Jul 11, 2018):
On a side note,
--overlayand--privateseem to work well enough. So you might be able to dofirejail --private="/path/to/application/home" --overlay-named="Application name"and it might work?@laenion commented on GitHub (Jul 11, 2018):
Oh, sorry, I was originally using
--private=(otherwise the home directory contents wouldn't be persistent) and was testing some more combinations. But as the warning already says combining the options with--overlayis not working in either case - only pure--privatedoes.@chiraag-nataraj commented on GitHub (Jul 11, 2018):
Huh, this is weird.
firejail --overlay --private="."works for me, but e.g.firejail --overlay --private="~/tmp"doesn't.