At the moment it is not possible to update the tunnel config to point to a docker hostname.
Assume the following docker-compose.yaml:
services:
crafty:
image: registry.gitlab.com/crafty-controller/crafty-4:latest
container_name: crafty
restart: always
networks:
- crafty
playit:
container_name: playit
image: ghcr.io/playit-cloud/playit-agent:latest
restart: always
environment:
SECRET_KEY: "${SECRET_KEY}"
networks:
- crafty
networks:
crafty:
To get this to work in you have to set the tunnel to Local Address: crafty and Local Port: 25565
But it is not possible to set the Local Address as a hostname, only IPs are possible
Workaround:
services:
crafty:
image: registry.gitlab.com/crafty-controller/crafty-4:latest
container_name: crafty
restart: always
networks:
crafty:
ipv4_address: '10.1.0.100'
playit:
container_name: playit
image: ghcr.io/playit-cloud/playit-agent:latest
restart: always
environment:
SECRET_KEY: "${SECRET_KEY}"
networks:
- crafty
networks:
crafty:
driver: bridge
ipam:
config:
- subnet: 10.1.0.0/16
By giving the container a 'static' IP it is possible to setup the Tunnel via the IP
But this requires more configuration and doesn't look clean
At the moment it is not possible to update the tunnel config to point to a docker hostname.
Assume the following docker-compose.yaml:
To get this to work in you have to set the tunnel to
Local Address: craftyandLocal Port: 25565But it is not possible to set the Local Address as a hostname, only IPs are possible
Workaround:
By giving the container a 'static' IP it is possible to setup the Tunnel via the IP
But this requires more configuration and doesn't look clean