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
Hello,
I use colima since yesterday, I have a dns container working perfectly with docker, since I use colima, Ihave this problem: docker: Error response from daemon: driver failed programming external connectivity on endpoint nice_bell (b688f5012ab945b7d85e4f85a1ead26960501561deb75c417db4333e27b85db7): failed to bind port 0.0.0.0:53/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use.
(same with udp),
When I use 54 port (for exemple), it work fine.
Maybe it's a permissions problem or something like that?
I tested with netcat before in addition to lsof (by listening to port 53 directly).
Since we did not find a solution, we installed a dnsmasq and it works perfectly but not with docker-compose with colima (works with docker desktop).
Description
Hello,
I use colima since yesterday, I have a dns container working perfectly with docker, since I use colima, Ihave this problem:
docker: Error response from daemon: driver failed programming external connectivity on endpoint nice_bell (b688f5012ab945b7d85e4f85a1ead26960501561deb75c417db4333e27b85db7): failed to bind port 0.0.0.0:53/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use.
(same with udp),
When I use 54 port (for exemple), it work fine.
Maybe it's a permissions problem or something like that?
Version
colima version 0.7.5
git commit: 1588c06
runtime: docker
arch: aarch64
client: v27.2.1
server: v27.1.1
limactl version 0.23.2
qemu-img version 9.1.0
Operating System
Output of
colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/julian/.colima/default/docker.sock
Reproduction Steps
Expected behaviour
same as docker run -p 54:54 -it --rm alpine ash
Additional context
No response
The text was updated successfully, but these errors were encountered: