Comment on page
Use system home
How to use the system home and not the sandboxed one
Warning, this procedure can expose your system (and therefore your personal files) to dangers, as we are going to break the Bottles sandbox.
Each user has a personal homedir (
/home/your_username), this is the place where you can store your personal files, like videos, photos or documents. This path is also used for cache files
.cacheand software configurations
|_ Program Files/
|_ Program Files (x86)/
It generates a folder in the
users/path, for the current logged in user (e.g. I'm currently logged as
mirko, so the runner will create a
users/. It also creates a Public folder, but that is not our interest right now.
Each user folder contains some symlink to the original homedir:
|_ Desktop -> ~/Desktop
|_ Documents -> ~/Documents
|_ Downloads -> ~/Downloads
|_ Music -> ~/Music
|_ Pictures -> ~/Pictures
|_ Saved Games
|_ Videos -> ~/Videos
So each program installed in the bottle can see your files from the linked folders.
Starting from Bottles 2021.10.14, the userdir path is sandboxed, so the above symlinks don't exist.
Creating a new bottle, Bottles detect if it is running under Flatpak, then remove these symlinks and make them as normal folders inside the bottle. As a result, each program can only work with files inside the sand-boxed userdir (shareable across programs).
While this is a practice discouraged by Bottles and we take no responsibility for what may happen after exposing your homedir to the runner, there is a very simple way to do it.
then find the bottle you want to give access to the homedir (e.g. it is called Testing in our case), so move to the userdir:
cd Testing/drive_c/users/your_username/ && ls -l
remove the folders you want to expose (e.g. Documents):
rm -r Documents
then recreate as symlink (e.g. for Documents):
ln -s ~/Documents Documents
and this is all!