dnsmasq conflict
See original GitHub issueKeep getting the error when I run docker-compose up or build
ERROR: Service "cli" mounts volumes from "amazeeio-ssh-agent", which is not the name of a service or container.
When I did pygmy up it fails
Error: failed to start containers: amazeeio-dnsmasq
/var/lib/gems/2.3.0/gems/pygmy-0.9.8/lib/pygmy/docker_service.rb:13:in `start': Failed to run amazeeio-dnsmasq. Command docker run -d -p 53:53/tcp -p 53:53/udp --name=amazeeio-dnsmasq --cap-add=NET_ADMIN andyshinn/dnsmasq:2.75 -A /docker.amazee.io/127.0.0.1 failed (RuntimeError)
from /var/lib/gems/2.3.0/gems/pygmy-0.9.8/bin/pygmy:120:in `exec_up'
from /var/lib/gems/2.3.0/gems/pygmy-0.9.8/bin/pygmy:33:in `up'
from /usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run'
from /usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in `invoke_command'
from /usr/lib/ruby/vendor_ruby/thor.rb:369:in `dispatch'
from /usr/lib/ruby/vendor_ruby/thor/base.rb:444:in `start'
from /var/lib/gems/2.3.0/gems/pygmy-0.9.8/bin/pygmy:300:in `<top (required)>'
from /usr/local/bin/pygmy:22:in `load'
from /usr/local/bin/pygmy:22:in `<main>'
Followed lagoon documentation fully. I am on Ubuntu 17: Additional port information as follow:
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 10984/dnsmasq
tcp 0 0 192.168.1.105:53 0.0.0.0:* LISTEN 10984/dnsmasq
tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 10984/dnsmasq
tcp 0 0 172.18.0.1:53 0.0.0.0:* LISTEN 10984/dnsmasq
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1865/dnsmasq
tcp6 0 0 ::1:53 :::* LISTEN 10984/dnsmasq
tcp6 0 0 fe80::b52c:90c0:550f:53 :::* LISTEN 10984/dnsmasq
udp 0 0 0.0.0.0:5353 0.0.0.0:* 8258/chrome
udp 0 0 0.0.0.0:5353 0.0.0.0:* 894/avahi-daemon: r
udp 0 0 127.0.0.1:53 0.0.0.0:* 10984/dnsmasq
udp 0 0 192.168.1.105:53 0.0.0.0:* 10984/dnsmasq
udp 0 0 172.17.0.1:53 0.0.0.0:* 10984/dnsmasq
udp 0 0 172.18.0.1:53 0.0.0.0:* 10984/dnsmasq
udp 0 0 127.0.1.1:53 0.0.0.0:* 1865/dnsmasq
udp6 0 0 :::5353 :::* 8258/chrome
udp6 0 0 :::5353 :::* 894/avahi-daemon: r
udp6 0 0 ::1:53 :::* 10984/dnsmasq
udp6 0 0 fe80::b52c:90c0:550f:53 :::* 10984/dnsmasq
unix 2 [ ACC ] STREAM LISTENING 55394 5801/code --unity-l /run/user/1000/vscode-ce967cf1-1.23.1-main.sock
unix 2 [ ACC ] STREAM LISTENING 50351 5853/app --node-int /run/user/1000/vscode-ce967cf1-1.23.1-shared.sock
unix 2 [ ACC ] STREAM LISTENING 31253 1581/tor /var/run/tor/control
unix 2 [ ACC ] STREAM LISTENING 45314 4941/Keybase /tmp/.org.chromium.Chromium.jQeMvP/SS
unix 2 [ ACC ] STREAM LISTENING 19253 1/init /run/cups/cups.sock
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
How to avoid conflicts between dnsmasq and systemd ...
If you're using a default Ubuntu 18.04 setup, this may be caused by a conflict between systemd-resolved (the default DNS server) and dnsmasq...
Read more >Multipass wants to occupy port 53 with dnsmasq
Hello. I'm on Ubuntu 20.04.1 Server. When installing multipass, it also tries to start dnsmasq on port 53, which conflicts with my existing ......
Read more >[SOLVED] dnsmasq.service conflict with systemd-resolved ...
Lately I noticed that dnsmasq.service was failing to start by giving the following error message. ( ...
Read more >How to avoid conflicts between dnsmasq and systemd ...
Issue. How to avoid conflicts between dnsmasq and systemd-resolved ? Environment. Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8 ...
Read more >[Dnsmasq-discuss] Avoid conflicts between dnsmasq and ...
[Dnsmasq-discuss] Avoid conflicts between dnsmasq and systemd-resolved. Dominick C. Pastore dominickpastore at dcpx.org
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sher1 and you’re running it with
pygmy up --no-resolver
?@rtprio I did not, that was the magic I needed. Thanks!