Skip to content
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

Issue using vopono with non-steam games in steam because of sudo requirement #257

Open
ParetoOptimalDev opened this issue Mar 17, 2024 · 1 comment

Comments

@ParetoOptimalDev
Copy link

Related to #189.

For instance:

Target: vopono
launch options: exec stremio

Results in:

/bin/sh\0-c\0/home/pod/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2597603739 -- /home/pod/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- vopono exec stremio\0
chdir "./"
 2024-03-17T07:53:46.557Z INFO  vopono_core::util > Calling sudo for elevated privileges, current user will be used as default user
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
Uploaded AppInterfaceStats to Steam
@ParetoOptimalDev ParetoOptimalDev changed the title Issue using vopono with steam because of sudo requirement Issue using vopono with non-steam games in steam because of sudo requirement Mar 17, 2024
@jamesmcm
Copy link
Owner

Does it work if you use the firejail approach here - https://github.com/jamesmcm/vopono/blob/master/USERGUIDE.md#creating-only-network-namespace ? - i.e. using vopono first separately to generate only the network namespace.

Also since it seems to be running in a container anyway, you might be able to specify the container to use the created network namespace directly, but I'm not familiar with the Steam launch wrapper details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants