Need help: accessing all my containers by name

jrbaconcheese@yall.theatl.social to Selfhosted@lemmy.world – 45 points –

I’m to the point now where my little home device has enough services and such that bookmarking them all as http://nas-address:port is annoying me. I’ve got 3 docker stacks going on (I think) and 2 networks on my Synology. What’s the best or easiest way to be able to reach them by e.g. http://pi-hole and such?

I’m running all on a Synology 920+ behind a modem/router from my ISP so everything is on 192.168.1.0/24 subnet, and I’ve got Tailscale on it with it as an exit node if that helps.

34

You are viewing a single comment

Everybody is saying a reverse proxy which is correct, but you said docker stacks, so if that means docker compose then the names of your container is also in DNS so you can use that.

Can't remember if port is needed still or not however.

AFAIK docker-compose only puts the container names in DNS for other containers in the same stack (or in the same configured network, if applicable), not for the host system and not for other systems on the local LAN.

If you don't set the network, doesn't it default to host?

I'm pretty sure it's available locally... Yes but maybe not via network. So might not be as useful for OP. Correct!

4 more...
4 more...