Able to launch first container, but after then its failing for launching another container. On debugging found that address, 172.23.0.3 is already allocated to dhcp interface by neutron and driver is trying to assign same to newly created container.
root@vikas-VirtualBox:/home/vikas/kuryr# docker run --net=neta1 -itd --name=ct1 busybox
85817ce18afe505a23d76cb87eb6dc549c0660b0c1113940c5f645f2f8080071
root@vikas-VirtualBox:/home/vikas/kuryr# docker run --net=neta1 -itd --name=ct2 busybox
ca4903aa1ba7fb684a75c3fbb1813163d8b56b9d935e385767a62f887f1ba769
Error response from daemon: Cannot start container ca4903aa1ba7fb684a75c3fbb1813163d8b56b9d935e385767a62f887f1ba769: failed to create endpoint ct2 on network neta1: Plugin Error: NetworkDriver.CreateEndpoint, {
"Err": "Unable to complete operation for network 6b597531-eb23-44f7-98d3-92f04bed6cb2. The IP address 172.23.0.3 is in use."
}
root@vikas-VirtualBox:/home/vikas/kuryr# docker run --net=neta1 -itd --name=ct3 busybox
96b47f08ca08434209d16458b80ca73bbadd006e19e61c7f773b74485b0c5366
Error response from daemon: Cannot start container 96b47f08ca08434209d16458b80ca73bbadd006e19e61c7f773b74485b0c5366: failed to create endpoint ct3 on network neta1: Plugin Error: NetworkDriver.CreateEndpoint, {
"Err": "Unable to complete operation for network 6b597531-eb23-44f7-98d3-92f04bed6cb2. The IP address 172.23.0.3 is in use."
}
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 181f2bf72996bed
Author: Vikas Choudhary <email address hidden>
Date: Tue Nov 3 13:52:51 2015 +0530
Create subnets with dhcp disabled
This fix is intended to disable dhcp for subnets created. If dhcp is
enabled, driver has no information about ip address allocated to dhcp
namespace interface and eventually tries to allocate same ip address to
container and this leads to exception from neutron saying "The IP
address is in use."
Change-Id: If598cacb475ab4
Closes-Bug: #1512341