mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #685] --overlay creates files owned by root. Should it? #470
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#470
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 @vn971 on GitHub (Aug 5, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/685
see subj. It's a bit inconvenient because I can't delete files then.
Thoughts?
@netblue30 commented on GitHub (Aug 7, 2016):
I need it as root, otherwise overlayfs will not work. I put in a new command line option --overlay-clean that removes all the overlays in ~/.firejail
@vn971 commented on GitHub (Aug 7, 2016):
@netblue30 Thanks for the explanations!
Can firejail make all directory owners as
root:user, and make the group able to modify the files (chmod g+rw)?@netblue30 commented on GitHub (Aug 9, 2016):
I'll look into it, but is very unlikely. It has something to do with the way they implemented overlayfs.