Custom network addresses in compose

[Svenum]

I would love to use Pelican, but the docker netowrk "pelican-nw" uses the same ip range as my physical network.
It would be handy if there was a way to configure the ipv4/ipv6 network manually via the compose.yml

[SubstituteR]

You should be able to configure the network settings from within your config.yml.

Here's an example with the default / unconfigured

docker:
  network:
    interface: 172.18.0.1
    dns:
    - 1.1.1.1
    - 1.0.0.1
    name: pelican_nw
    ispn: false
    IPv6: true
    driver: bridge
    network_mode: pelican_nw
    is_internal: false
    enable_icc: true
    network_mtu: 1500
    interfaces:
      v4:
        subnet: 172.18.0.0/16
        gateway: 172.18.0.1
      v6:
        subnet: fdba:17c8:6c94::/64
        gateway: fdba:17c8:6c94::1011

You can also refer to the pterodactyl documentation for custom networks, which should be mostly, if not completely, the same with Pelican.

[Svenum]

yeah, that is true, but it would be simpler to just set the CIDR like 172.18.0.0/16 via an env to set this

[QuintenQVD0]

In the latest release of wings, if the subnet is not free wings will auto try to find the next free one