So my question is, what is the best way to remediate the issue:

Option 1: I could create a new network and assign containers to it thusly.

spoiler 
docker network create --subnet=192.168.0.0/24 bridge_2

# Then adjust the compose file to reflect the new network

    restart: always
    networks:
      bridge_2:
        aliases:
          - my_container

networks:
  bridge_2:
    external: true

Option 2: I could modify Docker’s network configuration to increase the address pool for networks thusly:

spoiler 
nano /etc/docker/daemon.json

# Then edit thusly

{
  "default-address-pools": [
    {
      "name": "bridge_2",
      "subnet": "10.10.0.0/16",
      "gateway": "10.10.0.1"
    }
  ]
}

Which would be best practice? Which would you choose for your network? Or, is there a better way?

'presh

  • irmadlad@lemmy.worldOPEnglish
    3·
    6 days ago

    I know I’ll smoke a turd in hell for this but, I am not very IPv6 knowledgeable. Old head, old school, old ways. I would seem to solve a lot of problems tho. Perhaps I should spool up to 2025. LOL