This message was deleted.
# k3d
a
This message was deleted.
w
192.169.7.x is the subnet of your external docker network? You'd need a way to specify the IP of the node containers that k3d spins up. There's currently no option in k3d to do so. Feel free to open a feature request though 👍
v
My docker network config looks like this:
Copy code
networks:
  dc1:
    driver: bridge
    ipam:
     config:
       - subnet: 10.5.0.0/16
  dc2:
    driver: bridge
    ipam:
     config:
       - subnet: 10.6.0.0/16
  wan:
    driver: bridge
    ipam:
     config:
       - subnet: 192.169.7.0/24
         gateway: 192.169.7.1
Essentially, I want k3d to play on the WAN network, which is the ingress/egress network where I'm federating multiple consul clusters. For consistency reasons, I really want it statically assigned.