Hi guys! I have several docker containers running on my home server set up with separated compose files for each of them, including a Pihole one that serves as my home DNS. I created a network for it and a fixed IP but I couldn’t find a way to set fixed IPs to the other containers that use the Pihole network. Well everything works but every now and then I have problems because the Pihole cant start first and grab the fixed IP and some other container gets its IP so nothing works because everything depends on the Pihole to work. My Pihole compose is like this:

`networks: casa:

driver: bridge
ipam:
  config:
    - subnet: "172.10.0.0/20"

networks:

  casa:
    ipv4_address: 172.10.0.2`

My Jellyfin container as an example is like this:

`_networks: - pihole_casa dns: - 172.10.0.2

networks: pihole_casa: external: true__`

I read the documentation about setting fixed IP but all I got was using one single compose file and with 12 containers that seems like a messy solution… I couldn’t set fixed IPs with different compose files. Do you guys have any suggestion about it?

Thanks!

TLDR: I want to set fixed IPs to containers in different compose files so all of them use Pihole as DNS and don´t steal Pihole’s IP in the startup

  • fernandu00OP
    2·
    2 years ago

    Maybe I’m the one missing something. Are you saying I just have to use the LAN IP adress in the dns line in the compose file? I used the docker IP adress because I had some issues with containers not communicating with each other because every time I create a new container docker creates a new network for it. I’m gonna give it a try once I get home. Thanks!

    • 名探偵@lemmy.dbzer0.com
      2·
      2 years ago

      For each container you can specify what network to use. For example:

      networks:
  - network1
  - network2

      Then set the same network for the containers that should be able to communicate and you can just use the name of the service instead of the fixed ip. There is also hostname which can be set on each container.

      You can also use the same network with multiple compose files.

      Create the network like this docker network create http_network and put this in your compose files:

      networks:
  http_network:
    external: true
      • fernandu00OP
        1·
        2 years ago

        That external part I’ve set in my compose files but I didn’t know about the hostname …thanks!

    • 𝙚𝙧𝙧𝙚@feddit.win
      2·
      2 years ago

      If you configure the network externally and configure each service to use the external network… then each should be able to communicate with each other using the service names. No need for static IP addresses.

      See: https://docs.docker.com/compose/networking/

      Relevant bit:

      When you run docker compose up, the following happens:

      A network called myapp_default is created. A container is created using web’s configuration. It joins the network myapp_default under the name web. A container is created using db’s configuration. It joins the network myapp_default under the name db.

      Each container can now look up the hostname web or db and get back the appropriate container’s IP address. For example, web’s application code could connect to the URL postgres://db:5432 and start using the Postgres database.

      • fernandu00OP
        1·
        2 years ago

        I thought that worked only within the same compose file … And I ignored the documentation page because I thought it was obsolete …thanks!