Devilbox_bind_1 Cannot start service bind

Community Discussions
1

After My Docker automatically update, this happen to all my devilbox (in 2 windows pc have the same errors).
I have checked my port, and nothing use port 53.

Creating network “devilbox_app_net” with driver “bridge”
Creating devilbox_bind_1 …
Host is already in use by another container
Creating devilbox_bind_1 … error

ERROR: for devilbox_bind_1 Cannot start service bind: driver failed programming external connectivity on endpoint devilbox_bind_1 (aba176sQykNT8e3qQvtoxp7koaCrdcEVQgQK9f9d31d08db3a0a2df2894191633): Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use

ERROR: for bind Cannot start service bind: driver failed programming external connectivity on endpoint devilbox_bind_1 (aba176sQykNT8e3qQvtoxp7koaCrdcEVQgQK9f9d31d08db3a0a2df2894191633): Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use
Encountered errors while bringing up the project.

2

There was a Docker issue present on version 3.2.1 that caused this error. The issue is discussed here:

There was a patch released just this week that solves that problem. Affected users were not only Devilbox users but anyone who used BIND in Docker.
P.