Comment on Problem connecting to host from Docker container

• webuge@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

  I think it would be easier to use only one docker compose file with all services, and use the same network across all of them

  source

  • Jerry1098@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    But the network is created externally, so shouldn’t this be the same?

    source

    • webuge@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

      I didn’t read the docker files with attention in the first time, but since you have an external network it should work.

      source
    • Discover5164@lemm.ee ⁨1⁩ ⁨year⁩ ago

      yes is the same, or at least should.

      source
  • Jerry1098@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    And container to container works fine, im able to communicate p.e. with keycloak:9000

    source

    • webuge@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

      Do you have coddy to point the DNS to your keyckloak instance like in this part of the tutorial? auth.gurucomputing.com { reverse_proxy keycloak:8080 }

      Also do you have the domain registered?

      source
• Discover5164@lemm.ee ⁨1⁩ ⁨year⁩ ago

  this is a long shot but the keycloack container is connected to 2 networks, does this couse a problem?

  i’m saying this because traefik need you to specify on the labels which docker network it should use. maybe there is something similar.

  but as i said this is a very long shot and it’s probably bs

  source