Implement printing published ports

[rumpl]

❯ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                  PORTS                                                  NAMES
9126fca893ca        nginx               "nginx -g 'daemon of…"   23 seconds ago      Up Less than a second   0.0.0.0:80->80/tcp, 0.0.0.0:8000-9000->8000-9000/tcp   hopeful_banzai

❯ ./bin/docker --context moby ps
CONTAINER ID        IMAGE        COMMAND                       STATUS                       PORTS
9126fca893ca        nginx        nginx -g 'daemon off;'        Up Less than a second        0.0.0.0:80->80/tcp, 0.0.0.0:8000-9000->8000-9000/tcp

[chris-crone]

LGTM

[thaJeztah]

In case it's useful, I implemented some presentation logic for ports in the CLI a while back (see docker/cli#581)

I also recently discovered that there's a weird discrepancy between services and containers when publishing port-ranges (still to investigate further);

For a service (docker service create);

-p 8080-8090:80 means: map container port 80 to ports 8080 - 8090 on the host

For a container;

-p 8080-8090:80 means: map container port 80 to the first available port within 8080 - 8090

I never realised this discrepancy was there tbh (as mentioned; need to investigate further if this was on purpose or an oversight)

[silvin-lubecki]

LGTM