You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to use --private but have directories in the sandbox ~/.mozilla/firefox/<profile name> and ~/Downloads persistent only disk? Currently I use --private-dir=/.firejail/<profile name> but it keeps all the rest of files in their $HOME which are not important to me (and possibly Firefox) like their own .bashrc,.cache/, etc.--I would prefer them to be on tmpfs so they are not taking up disk space and never get to the point of the files being staled since they are wiped when sandbox closes and freshly generated when it starts again.
Also I'm looking to profiles-sync-daemon, any tips on using the two together? I think I can migrate the profiles by moving them from /.firejail/<profile_name> to ~/.mozilla/firefox/<profile_name> and then manage them with the single un-sandboxed ~/.mozilla/firefox/profiles.ini (--private-dir=/.firejail/<profile name> meant each of my profiles was using their own profiles.ini)--is that all that should be needed? What prompted the initial question is that I would prefer not to have the sandboxed profiles each having their own $HOME in e.g. /.firejail but their profile paths separate at ~/.mozilla/firefox/<profile_name>--the profile path should obviously be persistent but I think the rest of $HOME don't need to be (since I have dozens of profiles this is probably a little more of an issue than it is).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to use
--privatebut have directories in the sandbox~/.mozilla/firefox/<profile name>and~/Downloadspersistent only disk? Currently I use--private-dir=/.firejail/<profile name>but it keeps all the rest of files in their$HOMEwhich are not important to me (and possibly Firefox) like their own.bashrc,.cache/, etc.--I would prefer them to be on tmpfs so they are not taking up disk space and never get to the point of the files being staled since they are wiped when sandbox closes and freshly generated when it starts again.Also I'm looking to profiles-sync-daemon, any tips on using the two together? I think I can migrate the profiles by moving them from
/.firejail/<profile_name>to~/.mozilla/firefox/<profile_name>and then manage them with the single un-sandboxed~/.mozilla/firefox/profiles.ini(--private-dir=/.firejail/<profile name>meant each of my profiles was using their ownprofiles.ini)--is that all that should be needed? What prompted the initial question is that I would prefer not to have the sandboxed profiles each having their own$HOMEin e.g./.firejailbut their profile paths separate at~/.mozilla/firefox/<profile_name>--the profile path should obviously be persistent but I think the rest of$HOMEdon't need to be (since I have dozens of profiles this is probably a little more of an issue than it is).Beta Was this translation helpful? Give feedback.
All reactions