You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a container has been created with a static IP address, then removed, no new container attach to that static IP address, thereby rendering that IP address unusable. Also cannot remove a static IP address from a container network.
Environment information
This a 2-node vSAN.
vSphere and vCenter Server version
Server Version: v1.5.5-21324-50a44954
Storage Driver: vSphere Integrated Containers v1.5.5-21324-50a44954 Backend Engine
VMware Product: VMware vCenter Server
VMware OS version: 6.7.0
docker create --name web --net vch1-containers --ip 192.168.250.10 nginx:latest
docker network connect db-net web
docker start web
docker create --name web nginx:latest
docker network connect vch1-containers --ip 192.168.250.10 web
docker network connect db-net web
docker start web
Actual behavior
Error response from daemon: Server error from portlayer: Cannot reserve IP range 192.168.250.10 - 192.168.250.10. Already in use
Error: failed to start containers: web
Expected behavior
I expect the container to start with the container ip address of 192.168.250.10
Logs
No logs
See also
Troubleshooting attempted
Searched GitHub for existing issues. (Mention any similar issues under "See also", above.)
Searched the documentation for relevant troubleshooting guidance.
I tried to first disconnect the IP address from the container network, but I receive an error.
docker network disconnect web vch1-containers
Error response from daemon: vSphere Integrated Containers does not yet implement DisconnectContainerFromNetwork
The text was updated successfully, but these errors were encountered:
Summary
If a container has been created with a static IP address, then removed, no new container attach to that static IP address, thereby rendering that IP address unusable. Also cannot remove a static IP address from a container network.
Environment information
This a 2-node vSAN.
vSphere and vCenter Server version
Server Version: v1.5.5-21324-50a44954
Storage Driver: vSphere Integrated Containers v1.5.5-21324-50a44954 Backend Engine
VMware Product: VMware vCenter Server
VMware OS version: 6.7.0
VIC version
vSphere Integrated Containers v1.5.5-21324-50a44954 Backend Engine: RUNNING
VCH configuration
vic-machine-windows.exe create
--target='root:[email protected]' --user=[email protected] --password='lwwerkwerwerw'
--no-tlsverify --thumbprint=dshfksdfhksdhkfhsdfhsdhfk --no-tls
--compute-resource=ClusterDev
--image-store=vsanDatastoreDev/vch1-images
--volume-store vsanDatastoreDev/vch1-volumes:default
--bridge-network vch1-bridge
--public-network vch1-public
--public-network-ip 192.168.254.1/24
--public-network-gateway 192.168.254.1
--dns-server 192.168.250.88
--container-network vic-containers:vch1-containers
--container-network-ip-range vic-containers:192.168250.0/24
--container-network-gateway vic-containers:192.168250.1/24
--container-network-dns vic-containers:192.168.250.88
--container-network-firewall vic-containers:published
--name vch1
Details
Steps to reproduce
docker create --name web --net vch1-containers --ip 192.168.250.10 nginx:latest
docker network connect db-net web
docker start web
docker create --name web nginx:latest
docker network connect vch1-containers --ip 192.168.250.10 web
docker network connect db-net web
docker start web
Actual behavior
Error response from daemon: Server error from portlayer: Cannot reserve IP range 192.168.250.10 - 192.168.250.10. Already in use
Error: failed to start containers: web
Expected behavior
I expect the container to start with the container ip address of 192.168.250.10
Logs
No logs
See also
Troubleshooting attempted
I tried to first disconnect the IP address from the container network, but I receive an error.
docker network disconnect web vch1-containers
Error response from daemon: vSphere Integrated Containers does not yet implement DisconnectContainerFromNetwork
The text was updated successfully, but these errors were encountered: