@crosbymichael I think the container should only be presented with the environment variables when the -p option is specified for port(s) that the containers EXPOSE.

The ip seems like a sticky area.

One option would be to populate an environment variable with the ip if it was specified with the -p option as well (e.g. ip::containerPort as in 10.10.10.2::8080) so you might get something like this:

SELF_8080_TCP_PORT=49153
SELF_8080_IP=10.10.10.2

However, if you use 0.0.0.0 that isn't helpful (e.g. 0.0.0.0:8080:8080).

Maybe the host isn't included in this; maybe the host would have to be passed in with -e as you would today. The port would still be super helpful though in cases where you are relying on Docker to bind to a random free port.

Introspection of external port #1270

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions