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
I want to either remove the NET_ADMIN capability or document why it is needed.
Reason for change
I am able to run the docker image using podman without the NET_ADMIN capability, so I don't see a reason for the container to have those capabilities. I have been only using sunshine and moonlight, so this might be a steam remote play issue which I cant test right now. In any case however this seems to be the only undocumented parameter.
Proposed code change
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
NET_ADMIN is needed for steam remote play specifically spoofing the IP if setting the host, I found that was needed when using a Linux host and a Windows client.
As far as requirements the only hard requirements are apparmor and seccomp unconfined as steam will not run without it, the rest is optional.
Is this a new feature request?
Wanted change
I want to either remove the NET_ADMIN capability or document why it is needed.
Reason for change
I am able to run the docker image using podman without the NET_ADMIN capability, so I don't see a reason for the container to have those capabilities. I have been only using sunshine and moonlight, so this might be a steam remote play issue which I cant test right now. In any case however this seems to be the only undocumented parameter.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: