Default listen port not being set to 8000

[matthewmrichter]

For releases after roughly tag 2.2.0, when we launch vault-ui in our Mesos/Marathon cluster, it seems to be listening on a random port rather than 8000 by default (as is specified in the README). I was able to resolve this by adding the PORT=8000 env variable via our Marathon template, which seems to force the port to 8000. But otherwise, it was spinning up on a random port and then failing our marathon health checks (which assumed 8000)

[ghost]

What command were you using to spin up the dockerings?

EDIT: I've checked my own docker file, and I haven't needed to add an ENV for port 8000. So I doubt this is an issue with the docker file.

[jodem]

On marathon looks like container port must be bound to the same host port, if you leave host port to 0 in marathon app definition (allowing marathon to pick a random port) the server won't respond to requests. As 8000 is not in the list of offered port I had to force let's say 17000 in host and container port and add the var env "PORT=17000" to have it work.

[jodem]

For info it turns out marathon add automatically PORT as var env in the container of the HOST port. Since vault-ui consider this value for an override of default value, docker correctly bind the port but vault-ui start locally on the bad port, host instead of local. That explains why in marathon (1.5.6 at least) we MUST force this PORT var env to be same as bound and host.