libnetwork
libnetwork copied to clipboard
moby
networking for containers
Signed-off-by: ZhiPeng Lu
This PR removes the restrictions on the null driver, providing a workaround for the issue discussed in https://github.com/moby/moby/issues/20547. We would like to be able to have a custom network driver...
I am trying to address https://github.com/docker/libnetwork/issues/1743 as part of this PR. There are two issues as part of this 1. When a node is power cycled unplanned or dockerd goes...
Signed-off-by: mingfukuang [email protected] **- What I did** when stop or delete one container with docker-proxy, stop container will call Unmap() to release port , func Unmap() need to acquire pm.lock.Lock()...
Creating `macvlan` network with single IP address range works, but attaching container fails. Create network: ``` $ docker network create -d macvlan \ --subnet 192.168.34.0/24 \ -o parent=eth0 \ --ip-range...
There is a longstanding issue over at https://github.com/docker/distribution/issues/785 where users reported connection resets trying to push to an AWS-hosted registry from inside the AWS network. After months, we've finally narrowed...
The primary driver of this issue is DHCP. The libnetwork remote API (as far as I understood it) has it contacting a network/IPAM remote plugin when a container is created...
We met "port already allocated" problem in our docker environment. It always happened after docker-daemon restarts abnormally or machine restarts abnormally. I read the related code, and found a possible...
> **Warning** > libnetwork was moved to https://github.com/moby/moby/tree/master/libnetwork > > libnetwork has been merged to the main repo of Moby since Docker 22.06. > > The old libnetwork repo (https://github.com/moby/libnetwork)...
This ticket resembles tickets from 2016 and earlier. For various reasons those are closed. My apologies if this is a duplicate or the problem is fixed in a newer version...
