Current Interlock:
Set the desired port in the INTERLOCK_DATA env var: -e INTERLOCK_DATA='{"port":80}'
Interlock NG:
Set the desired port in a label: --label interlock.port=80
Current Interlock:
Set the desired port in the INTERLOCK_DATA env var: -e INTERLOCK_DATA='{"port":80}'
Interlock NG:
Set the desired port in a label: --label interlock.port=80
FWIW I also verified this with the nginx extension as well. Both working as expected. If you continue to have issues please file an issue on github. Thanks!
This looks like it is working as expected:
The following gets port "80" exposed as it's the only port.
docker run --rm -ti -p 80:80 --hostname foo.local alpine ashIf more than one port is published I can specify which port to use:
docker run --rm -ti -p 80:80 -p 3000:3000 --label interlock.port=80 --hostname foo.local alpine ashYou can see the upstream is
172.17.0.1:80I can change the port specification for interlock and it adheres:
docker run --rm -ti -p 80:80 -p 3000:3000 --label interlock.port=3000 --hostname foo.local alpine ashHere I'm specifying port
3000instead of80.You can see the upstream selected is using port
3000.