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)

Morethanevil
link
fedilink
English
8
edit-2
3M

Add this to the service in your docker-compose.yml

  extra_hosts:
     - host.docker.internal:host-gateway

Example:

services:
    redis:
    restart: always
    container_name: redis
    image: redis:7.2-alpine
    extra_hosts:
      - host.docker.internal:host-gateway

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.

@Deemo@bookwormstory.social
creator
link
fedilink
English
23M

Thanks for the tip

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 124 users / day
  • 419 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog