VIC Docker Run Results in "error mapping ports: port ### is not available"
search cancel

VIC Docker Run Results in "error mapping ports: port ### is not available"

book

Article ID: 316994

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • When using docker run to map UDP ports, the container fails to start resulting in messages similar to the following.

# docker --tls run -p 1111:80/udp nginx
Unable to find image 'nginx:latest' locally
latest: Pulling from library/nginx
2a72cbf407d6: Pull complete
a3ed95caeb02: Pull complete
04b2d3302d48: Pull complete
e7f619103861: Pull complete
Digest: sha256:d903fe3076f89ad76afe1cbd0e476d9692d79b3835895b5b3541654c85422bf1
Status: Downloaded newer image for library/nginx:latest

docker: Error response from daemon: Server error from portlayer: error mapping ports: port 1111 is not available.



Environment

VMware vSphere Integrated Containers 1.x

Resolution

UDP port forwarding is currently unsupported. 

Workaround:
Use a container-network to attach the container directly to the network. Then use UDP via that interface. This will circumvent the traffic from going through the VCH endpoint VM allowing for non-tcp protocols.

Additional Information

Running containers port mapped with protocol fails "Server error from portlayer: error mapping ports" #7751