"detail": "The \"proxy\" address is invalid \"q1:8002\"" in docker-compose

when i use docker-compose, i got the error

config.json

{

  "listeners": {
    "*:8008": {
        "pass": "routes"
    }
 },
  "routes": [
      {
          "match": {
              "host": "a.test.com"
          },

          "action": {
            "proxy": "http://q2:8001"
           }
      },
      {
        "match": {
            "host": "b.test.com"
        },

        "action": {
          "proxy": "http://q1:8002"
         }
    } 
   ]
}

docker-compose.yml

version: "3"
services:
  center:
    build: "center"
    restart: always
    expose:
      - 443/tcp
      - 80/tcp
    ports:
      - 8008:8008
    links:
      - q1
      - q2

  q1:
    build: "q1"
    ports:
      - 8001:8001
  q2:
    build: "q2"
    ports:
      - 8002:8002

[mar0x]

Hello.
Currently, hostname resolving is not implemented in proxy specification. Please use exact ipv4 or ipv6 address.

@mar0x

thank you

[e1himself]

Hi here 👋

@mar0x Is there any plan on supporting hostnames for proxy directives?

I'm currently developing a prototype based on NGINX Unit with multiple sub-apps using docker-compose.yml to orchestrate services. Using IP addresses is inconvenient, as then I'd need to hard-code docker network addresses, which is not great.

Thanks!

[VBart]

@e1himself Hostnames there will require dynamic resolution. Also they can resolve to multiple IP addresses and different each time, which complicates everything even more. Probably, we will add it eventually, but no ETA yet.

Unit is made to have dynamic configuration and be updated in real time, why not just to put those addresses in the configuration as soon as they are getting known?

[buldezir]

tmp solution, example /docker-entrypoint.d/config.sh:

IP=$(getent hosts yourhostname | awk '{ print $1 }')
D=$(cat /path_to/config.json | sed "s/yourhostname:80/$IP:80/")
curl -X PUT -d "$D" --unix-socket /var/run/control.unit.sock http://localhost/config/

[glintik]

Hello. Currently, hostname resolving is not implemented in proxy specification. Please use exact ipv4 or ipv6 address.

Hi,

Any plans to implement support of hostnames? Using hostnames in docker compose files is an essential thing.