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

Regarding my previous blog post VMWare VIC vSphere Integrated Containers: Port mappings not working – Resolution:

I found it to behave randomly as a restart not always solved the reachability problems of my containers.

I restarted my search for a solution and found the following on GitHub: https://github.com/vmware/vic/issues/2316

Especially one of the last comments suggested, it may have something todo with dynamic VM allocation / balancing:

betazep commented on 15 Sep 2016

„Bummer. I figured it out. Apparently we have an infrastructure problem in our Lab vsphere cluster. Sometimes the containers were landing on a different host. When the containers are moved to the same host, everything works as expected. Thanks for the assist.“

We changed the allocation policy so that containers are always started on the same host as the Virtual Container Host, which resolves the problem. 
Notice: I don’t know if this works when moving machines with VMWare’s vMotion. 

 

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.