Closed pythoninthegrass closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Looking over the logs, could be related to Failed to gain CAP_SYS_ADMIN
. Will poke around to see if I can sort that out.
The host IP for route method is only for remote play, try it without that env var, it might not work in all environments. Sunshine works without it.
Looks like that was half the equation — commented out the HOST_IP
env var, then had to update the pacman db before being able to install anything. Was tripped up by the former, so couldn't complete the latter.
Edited env vars section:
environment:
- TZ=America/Chicago
- PUID=1000
- PGID=1000
- DRINODE=/dev/dri/renderD128
# - HOST_IP=192.168.192.161 # optional
- STARTUP=KDE # optional
- RESOLUTION=1920x1080 # optional
Now it runs as expected:
λ docker exec -it steamos bash
[root@steamos /]# pacman -S iputils
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'jupiter-staging' does not exist (use '-Sy' to download)
warning: database file for 'holo-staging' does not exist (use '-Sy' to download)
error: target not found: iputils
[root@steamos /]# pacman -Sy
:: Synchronizing package databases...
core downloading...
extra downloading...
multilib downloading...
jupiter-staging downloading...
holo-staging downloading...
[root@steamos /]# pacman -S --noconfirm iputils
resolving dependencies...
looking for conflicting packages...
Package (1) New Version Net Change Download Size
core/iputils 20221126-2 0.43 MiB 0.11 MiB
Total Download Size: 0.11 MiB
Total Installed Size: 0.43 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
iputils-20221126-2-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
installing iputils...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[root@steamos /]# ping google.com
PING google.com (142.251.116.138) 56(84) bytes of data.
64 bytes from rt-in-f138.1e100.net (142.251.116.138): icmp_seq=1 ttl=103 time=10.6 ms
64 bytes from rt-in-f138.1e100.net (142.251.116.138): icmp_seq=2 ttl=103 time=10.9 ms
^C
Thanks for your help @thelamer!
I do have the same problem using Unraid. Internet is not working when I access the steamos so I can't setup steam neither update it. Removing the HOST_IP does not fix the issue.
What's even worst is that it seems that launching this particular docker makes my entire Unraid server loosing internet, have to reboot the server without having that particular docker container launching on boot. The server will be back online until I start that container again.
It is being set as HOST for the network.
I do have the same problem using Unraid. Internet is not working when I access the steamos so I can't setup steam neither update it. Removing the HOST_IP does not fix the issue.
What's even worst is that it seems that launching this particular docker makes my entire Unraid server loosing internet, have to reboot the server without having that particular docker container launching on boot. The server will be back online until I start that container again.
It is being set as HOST for the network.
same :D no internet, i cant use it n bridge mode cause it wants to use 0.0.0.0:80 is already in use.
Issue still seems unresolved in Unraid even running on latest container update and Beta Unraid 7.0.0-beta.4.
Is there an existing issue for this?
Current Behavior
When launching the
docker-steamos
container, unable to access network interfaces, nor the internet in general.Expected Behavior
exec
or VNC into bespoke containerping
or open websitesSteps To Reproduce
docker compose up -d
Environment
Container logs