-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Network connection does not function for SteamOS container under Unraid #16
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
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. |
I'm having the same issue |
This seems to effect all KasmVNC based images so the advice has been to use the default bridge. |
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. |
It's not |
Is there an existing issue for this?
Current Behavior
Network connection does not function for SteamOS container under Unraid. Issue seems same as below closed bug but still occurs on latest container update and Beta Unraid 7.0.0-beta.4. Container not able to connect to internet and causes Unraid network stack to become unstable requiring unraid server reboot.
#4
Expected Behavior
Custom bridge network with dedicated static IP assigned to container from Unraid but still does not function properly.
Steps To Reproduce
Install container from Unraid app repo and set with network type as Custom BR0 with static IP. After install launch webui and login to Steam or access internet using firefox. Both report no internet access.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: