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
Still, choosing the --workdir seems not perfect (in either solution), but in my view it should at least not be host $HOME by default, if another HOME has been specified...
It would be good to protect the host's $HOME dir from applications in the container if a custom home is selected. Not mounting it at /home/<user> is a good start but it's still available through /run/host/home/<user> as things stand now. Sandboxing apps and isolating from personal files in $HOME is actually my main usage, but it's not the (current) way of the project.
Apologies, you might find this because GitHub links everything together and because I mentioned issues above, but I intended this as preparation / personal notes on my own fork.
I prefer that $HOME isn't mounted if a custom home was specified.
Draft implementation (WIP)
https://github.com/gunnarx/distrobox/tree/dont_mount_host_home
Still, choosing the --workdir seems not perfect (in either solution), but in my view it should at least not be host $HOME by default, if another HOME has been specified...
Some relevant notes:
which notes one of the problems (that appears also now) that --workdir set to a non-existing location will cause an error.
It would be good to protect the host's
$HOME
dir from applications in the container if a custom home is selected. Not mounting it at/home/<user>
is a good start but it's still available through/run/host/home/<user>
as things stand now. Sandboxing apps and isolating from personal files in $HOME is actually my main usage, but it's not the (current) way of the project.Although, here is a discussion of that:
The text was updated successfully, but these errors were encountered: