VMWare VIC vSphere Integrated Containers: Port mappings not working – Resolution

UPDATE: see https://blog.sevyls.net/?p=561

VMWare’s vSphere Integrated Containers makes a managed Docker environment look easily achievable within a known ecosphere.

But it comes with a bunch of downsides, one of them is unreliable port mappings.

If you try to get a container up and running again after the main process failed and the container exited, you usually remove the old container like this:

$ docker rm -f container-name

This is usually the right way to get rid of old or exited containers and make room for a container with the same name again.

After removing your container seems to start again normally:

$ docker run -p 8080:8080 -d –name container-name my-image-of-choice

The container’s log shows your process is up and running, the docker ps command lists it with the appropriate port mapping.

But the port seems to be filtered anyway and no mapping comes up:

$ nmap -p 8080
Starting Nmap 7.70 ( https://nmap.org ) at …
Nmap scan report for
Host is up (0.016s latency).

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Menlo; color: #000000}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Menlo; color: #000000; min-height: 16.0px}
span.s1 {font-variant-ligatures: no-common-ligatures}

8080/tcp filtered

Some way to tackle this:

I stopped the container again with

$ docker stop container-name

and again started it with

$ docker start container-name

and there you go, the port got mapped correctly again.

Some classic IT moment like this:

UPDATE: see https://blog.sevyls.net/?p=561

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.

Diese Website verwendet Akismet, um Spam zu reduzieren. Erfahre mehr darüber, wie deine Kommentardaten verarbeitet werden.