Using a subnet mask to publish a port, like 100.64.0.0/10?

General
, ,
1

We just started to use headscale server with tailscale clients to create a wireguard mesh network between VM nodes. It would be great to be able to easily publish Docker container ports only on those internal IPs.

But it seems publishing ports is only possible with fixed IPs, not with subnet masks, which could be used to automatically select the matching IP(s).

Example:

services:
  db:
    image: postgres
    restart: unless_stopped
    ports:
      - 100.64.0.0/10:5432:5432
    environment:
      POSTGRES_PASSWORD: example

It seems more and more wireguard VPNs are used, many more services beside tailscale/headscale exist nowadays, this could to be an important use case for the future.

Where is the right place to create a feature request for this?