[BUG] Using a custom docker network prevents startup

[NeurekaSoftware]

Describe the bug
Using a custom docker network prevents startup.

services:
  cup:
    image: ghcr.io/sergi0g/cup
    container_name: cup
    networks:
      - pangolin
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./config/cup.json:/config/cup.json
    command: -c /config/cup.json serve
    restart: unless-stopped

networks:
  pangolin:
    external: true

It sits at INFO Starting server, please wait... for a very long time. Removing the networks solves this problem.

[sergi0g]

Interesting. I'm using a very similar compose which works just fine. I'm running two instances of course, but you can see that both are connected to an external network. Cup has never had any issues with it.

services:
  cup-master:
    image: ghcr.io/sergi0g/cup:nightly
    command: -c /config.json serve
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /ext/lab/cup/config.boron.json:/config.json
    networks:
      - local
    deploy:
      labels:
        traefik.enable: "true"
        traefik.http.services.cup.loadbalancer.server.port: 8000
        app.id: cup
      placement:
        constraints:
          - node.labels.name==boron

  cup-node:
    image: ghcr.io/sergi0g/cup:nightly
    command: -c /config.json serve
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /ext/lab/cup/config.beryllium.json:/config.json
    networks:
      - local
    deploy:
      placement:
        constraints:
          - node.labels.name==beryllium
    ports:
      - published: 53001
        target: 8000
        protocol: tcp
        mode: host
    

networks:
  local:
    external: true

Try running it again with debug logging enabled: command: -d -c /config/cup.json serve. Maybe something it timing out.