The plugin works fine when creating new containers.
If I have an pre-existing container with a dhcp network assigned, when dockerd is started, the entire dockerd daemon becomes unresponsive when acquiring an address.
When started using dockerd -l debug
DEBU[2024-01-30T11:31:24.182790475+01:00] EnableService 66264b3f1f650a2a3ffa050c87cb63fe80dc1333f7650fd17eadb5f9d4d0647d START
DEBU[2024-01-30T11:31:24.182815499+01:00] EnableService 66264b3f1f650a2a3ffa050c87cb63fe80dc1333f7650fd17eadb5f9d4d0647d DONE
DEBU[2024-01-30T11:31:24.183107384+01:00] Assigning addresses for endpoint nginx_2's interface on network virbr0
Any call to the API or on commandline just hangs, e.g. docker ps.
Disabling the plugin resolves the issue. It also seems to be hidden -occasionally- when using debug mode, so there might be a timing or race condition involved.
The plugin works fine when creating new containers. If I have an pre-existing container with a dhcp network assigned, when dockerd is started, the entire dockerd daemon becomes unresponsive when acquiring an address.
When started using
dockerd -l debug
Any call to the API or on commandline just hangs, e.g.
docker ps
.Disabling the plugin resolves the issue. It also seems to be hidden -occasionally- when using debug mode, so there might be a timing or race condition involved.