-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to isolating games so that they could never touch my $HOME folder? #10898
Comments
Have you tried the |
My hunch for those is that they are guessing your home location based on the username. Think something like: Instead of: Maybe you can trick it into behaving correctly by manipulating the USER environment variable. |
In dota this is possible using |
Your system information
Please describe your issue in as much detail as possible:
I want to isolate the game from my $HOME folder, enforce them using a new home folder, I make several attempts, all of them either have some shortcoming or failed to execute.
I have noticed that, steam have some sandbox tools, but I don't know how to use them.
Steps for reproducing this issue:
The most recent attemp is that, using
export HOME=/me/fakehome
before steam is launched.This makes several game using the fakehome folder as its home, but there are many games (e.g., Factorio, Feud) which still write
~/.factorio
or~/.pref
rather than/me/fakehome/*
I also tried
export PRESSURE_VESSEL_HOME=/me/fakehome
, wish the pressure-vessel-wrap could using the new home rather than the real home, but it also fails.Factorio
still tried to access myHOME
folder.An ancient attempt is that, using sandboxes like
bubblewrap
to isolate the steam client, but it have a disadvantage:I have a program which use
nvml
library to tuning the mem frequency and gpu clock while playing games.This program have a suid bit which grants the ability to control the graphical cards. Unfortuantely, bubblewrap erase the owner to nobody, thus the program become a normal program, could no longer tuning the gpu clocks.
The text was updated successfully, but these errors were encountered: