Bind caddy to ipv6 only, via docker-compose

Help
2

So i’ve found something that looks a little better than what chat-gpt offered for the docker-compose.yaml

version: '3'
networks:
  default:
    name: 'proxy_network'
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    restart: unless-stopped
    volumes:
      - /opt/kuma-monitor/kumadata:/app/data
    ports:
      - 2052:3001
    labels:
      caddy: status.onepub.dev
      caddy.reverse_proxy: "* {{upstreams 2052}}"
  caddy:
    image: "lucaslorentz/caddy-docker-proxy:ci-alpine"
    ports:
      - "80:80"
      - "443:443"
    networks:
      - ip6net
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /opt/kuma-monitor/cadydata/:/data
    restart: unless-stopped
    environment:
      - CADDY_INGRESS_NETWORKS=proxy_network

networks:
   ip6net:
     enable_ipv6: true
     ipam:
       config:
         #- subnet: 2401:da80:1000:2::/64        
         - subnet: 2600:1900:4180:bfa7:0:0:0:0/64

I now get the following error:

 docker-compose up
Creating network "kuma-monitor_default" with the default driver
Creating network "kuma-monitor_ip6net" with the default driver
Recreating kuma-monitor_caddy_1 ... 
Recreating kuma-monitor_caddy_1       ... error
WARNING: Host is already in use by another container

ERROR: for kuma-monitor_caddy_1  Cannot start service caddy: driver failed programming external connectivity on endpoint kuma-monitor_caddy_1 (4ba40Recreating kuma-monitor_uptime-kuma_1 ... done

ERROR: for caddy  Cannot start service caddy: driver failed programming external connectivity on endpoint kuma-monitor_caddy_1 (4ba406b811375dea6cd837e76c6105840f991130627e9cd597b66458128c6463): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

So its clearly still trying to bind to ipv4 addresses. I guess the docker-compose file doesn’t actually give it any instructions to not bind to the ipv4 address.