Closed mildfuzz closed 5 years ago
localhost
, 0.0.0.0
and 127.0.0.1
all points to the container itself, in this case sickrage.
Try this from a terminal
# docker ps -q | xargs -n 1 docker inspect --format '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}} {{ .Name }}' | sed 's/ \// /'
This will list all containers and their docker-ip. From that list, try using the ip for transmission instead. If that does not work, try using the host ip instead. You can get that from
$ ip route show
Edit: if you use portainer you can see all the ip adresses from there
Useful command, but you'll want to use the the container hostname. The container IPs are dynamic.
Also, I see why this might be confusing. From the computer that hosts the docker containers, all network routing is handled by docker. This is why when you go to portainer for example, http://localhost:9000
, docker routes the traffic from your computer to the docker container. But when you are inside the container, for example if you got to portainer and want to add another endpoint and you use localhost
, that will no longer point to your computer, it will be portainer itself.
This is a security measure. Think of it as you can see into a container but the container can't see out.
That command is super useful, thanks :)
After installing both deluge and transmission along side Sickrage, I am unable to run a successful test in sickrage torrent.
I have tried
localhost
,0.0.0.0
,127.0.0.1
and the machines local IP and hostname along side the correct ports. Torrent services are running and accessible via web clients.My suspicion is that the sickrage container isn't able to call out for some reason, but I am not sure how I can evidence this.