`immich_proxy` won't stay on a docker network.
First of all, to avoid the XY problem:
I want to access immich at a special local subdomain, i.e.
immich.home.bb.
I intend to use pihole (local DNS) and caddy (reverse proxy).
All of the services are inside separate docker containers on a network with a bridge driver.
Here is my docker-compose.yml
When I inspect the docker network, immich_proxy is not the internal (not the exact name) network. When I try to manually add it using docker network connect internal immich_proxy it shows up for some time and then goes away. If I remove the networks block from the immich_proxy and just use ports with -"2283:8080" I can access the auth page on device-ip:2283. I was hoping to use reverse_proxy immich_proxy:8080 in my Caddyfile but I can't ping the immich_proxy container using docker compose exec caddy ping -c 5 immich_proxy. I can do this to the other containers on the docker network, i.e. nodejs.4 Replies
Is it crashing because it can't connect to immich-server and immich-web?
All the immich containers need to be on the same network AND the proxy and caddy need to be on the same one.
Yes, you are correct, I found this in the logs
Okay, I will add all of them to my internal network and report back.
All those containers need network internal. Or, a second network immich or something.
I don't see any network related to immich on my
docker network ls then where do the immich microservices communicate 😅
Is it implicit and are they on some "default" docker network?
Thank you this worked!