docker compose reverse port map without using Host network driver (--net=host)
from Deemo@bookwormstory.social to selfhosted@lemmy.world on 26 Jul 2024 13:50
https://bookwormstory.social/post/2239518
from Deemo@bookwormstory.social to selfhosted@lemmy.world on 26 Jul 2024 13:50
https://bookwormstory.social/post/2239518
Hi guys quick question say you run a a application on your localhost (example lets say couchdb runing directly on localhost:3434 not in docker).
Now you have a docker container (say caddy, ngnix, etc). Is there a way to allow docker container to acess localhost:3434 WITHOUT using the Host network driver (–net=host)
#selfhosted
threaded - newest
Have you tried the IP of the host? IIRC that should work.
You have a lot of options: docs.docker.com/network/drivers/
What’s specifically the issue with the host driver in this case?
I should elaborate. I want to switch from caddy to authentiks internal reverse proxy. By default authentik uses ports 9000 and 90443 and you have the option to change them to 80 and 443 via docker compose.
Using host mode throws a wrench in the ports and authentik is made of more than one container.
Add this to the service in your docker-compose.yml
Example:
Then you can reach your host from inside the container via
host.docker.internal:3434
host.docker.internal
is like your “localhost” on the host. It is a special DNS name.Thanks for the tip
host.docker.internal
stackoverflow.com/…/how-to-access-host-port-from-…
Put them on the same network
My solution is to create a docker network with the macvlan driver connected to a bridge interface on the host. Then you make the database listen on the bridge or just leave it on all interfaces. Don’t forget to configure the ips.
I can share my config later.
You can use the flag
in your container “myname” will resolve as the IP of your host.
documentation at: docs.docker.com/reference/cli/docker/…/run/#add-h…>