create/run -P (publish all exposed ports to random ports) is unsupported

[shadjiiski]

In docker it is possible to have a single or all of the exposed ports published to a random (not specified by the user) port. I have tried to achieve the same via docker CLI and remote API and it is not working on VIC.

VIC Version:

JFrog Bintray build 6511

Docker Code

# Publish a single port
curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -d '{"Image": "docker.io/kitematic/hello-world-nginx", "NetworkMode": "bridge", "PortBindings": {"80/tcp": [{"HostPort": ""}]}}' http:/containers/create?name=remote-test-1

# Publish all exposed ports
curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -d '{"Image": "docker.io/kitematic/hello-world-nginx", "NetworkMode": "bridge", "PublishAllPorts": true}' http:/containers/create?name=remote-test-2

VIC Code

#Publish a single port
curl -k -H "Content-Type: application/json" -d '{"Image": "docker.io/kitematic/hello-world-nginx", "NetworkMode": "bridge", "PortBindings": {"80/tcp": [{"HostPort": ""}]}}' https://$IP:2376/containers/create?name=remote-test-1

# Publish all exposed ports
curl -k -H "Content-Type: application/json" -d '{"Image": "docker.io/kitematic/hello-world-nginx", "NetworkMode": "bridge", "PublishAllPorts": true}' https://$IP:2376/containers/create?name=remote-test-2

Expected behavior:
Having port 80 published in all cases like in docker: (after both containers have been started)

docker ps
CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS              PORTS                     NAMES
47ba36a21cad        docker.io/kitematic/hello-world-nginx   "sh /start.sh"           2 minutes ago       Up About a minute   0.0.0.0:32793->80/tcp     remote-test-2
38daf3db7ad6        docker.io/kitematic/hello-world-nginx   "sh /start.sh"           3 minutes ago       Up About a minute   0.0.0.0:32792->80/tcp     remote-test-1

docker inspect remote-test-X
...
    "NetworkSettings": {
            ...,
            "Ports": {
                "80/tcp": [
                    {
                        "HostIp": "0.0.0.0",
                        "HostPort": "32792"
                    }
                ]
            },
            ...
    }
...

Actual behavior:
On VIC none of the containers has its ports published: (after both containers have been started)

 docker --tls ps
CONTAINER ID        IMAGE                                   COMMAND             CREATED             STATUS              PORTS                         NAMES
0cd8ce462aed        docker.io/kitematic/hello-world-nginx   "sh /start.sh"      18 minutes ago      Up 16 minutes                                     remote-test-2
91399d708c1f        docker.io/kitematic/hello-world-nginx   "sh /start.sh"      19 minutes ago      Up 16 minutes                                     remote-test-1

docker inspect remote-test-1
...
        "NetworkSettings": {
            ...,
            "Ports": {
                "80/tcp": [
                    {
                        "HostIp": "0.0.0.0",
                        "HostPort": ""
                    }
                ]
            },
        ...
        }
...

docker inspect remote-test-2
...
        "NetworkSettings": {
            ...,
            "Ports": {
                "80/tcp": null
            },
        ...
        }
...

[anchal-agrawal]

@shadjiiski For specifying a single port published to a random port - the functionality is there but docker ps doesn't show the port mapping. I've created #3004 for this.

I believe publishing all ports with -P or --publish-all isn't supported yet.

[shadjiiski]

@anchal-agrawal

For specifying a single port published to a random port - the functionality is there but docker ps doesn't show the port mapping

You are right, it works for a specific ports and is not working for all ports. However, neither docker inspect nor the remote API reveal the host port on which the application can be accessed. Actually, I needed to enable the ssh access to the VCH and then check the iptables rules to verify your comment.

[anchal-agrawal]

With my fix for #3004, both ps and inspect show the mapped port:

$ sudo docker -H 192.168.77.225:2376 --tls run -d -p 6379 redis:alpine
$ sudo docker -H 192.168.77.225:2376 --tls ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                            NAMES
577f3a9e380c        redis:alpine        "docker-entrypoint.sh"   5 weeks ago         Up 16 seconds       192.168.77.225:32768->6379/tcp   focused_einstein
$ sudo docker -H 192.168.77.225:2376 --tls inspect 5
...
            "Ports": {
                "6379/tcp": [
                    {
                        "HostIp": "0.0.0.0",
                        "HostPort": "32768"
                    }
                ]
            },
...

[mhagen-vmware]

This issue has gotten slightly off track, but Iceboxing the original request for support for --publish-all support as that is a feature that we will not be getting to by GA.

[anchal-agrawal]

Thanks @mhagen-vmware. I've updated the issue title.