Closed tholu closed 3 years ago
https://github.com/tighten/takeout/issues/209
Yah, thanks for opening it here. You've diagnosed it correctly; haven't found a permanent solution, but the temporary solution is indeed to valet stop
, restart Docker, and then you can valet start
again and they should work together.
https://github.com/docker/for-mac/issues/5186
Also related.
@mattstauffer Thanks for the references and the temporary solution!
Before executing docker
command, you should stop dnsmasq service. sudo brew services stop dnsmasq
Tried both (uninstalling valet & stopping dnsmasq) but still facing same issue.
Docker Desktop preview 3.1.0 (60984) was released on 2021-02-11 https://docs.docker.com/docker-for-mac/apple-m1/
I've been affected by this issue, so I upgraded to the new version of Docker Desktop preview and attempted various combinations of building Docker images and restarting Valet. So far, so good! I haven't encountered the Docker DNS "read: connection refused" error (yet). Unfortunately, I don't know the exact sequence of events that triggered the issue for me.
@tholu Can you upgrade to the latest Docker Desktop for M1 preview and report back if you're still seeing this issue?
@jason-klein Thanks, I just tried it and had no issues anymore. @RS-Roshi Does it fix the issue for you as well?
@jason-klein Thanks, I just tried it and had no issues anymore. @RS-Roshi Does it fix the issue for you as well?
@tholu yes brother I have solved this issue by restarting after uninstalling the laravel/valet going to try new docker version with valet running hope to get it working as they claim
Closing. Anyone who hits this issue please open a new issue referencing this.
Clear description of your problem
The dnsmasq server of valet breaks docker on MacOS Big Sur 11.2 (M1 Apple Silicon)
Expected behavior
Docker should work fine alongside Laravel valet.
Current behavior
Pulling images with docker is not working anymore when dnsmasq runs:
Steps to Reproduce
docker-compose pull
Output of these steps
Possible solution
dnsmasq config that is not breaking Docker, see also this Reddit comment (sorry, linking to Reddit sucks)
Diagnosis
valet/dnsmasq stopped intentionally to get Docker working again.
sw_vers
valet --version
cat ~/.config/valet/config.json
cat ~/.composer/composer.json
composer global diagnose
composer global outdated
ls -al /etc/sudoers.d/
brew config
brew services list
brew list --formula --versions | grep -E "(php|nginx|dnsmasq|mariadb|mysql|mailhog|openssl)(@\d\..*)?\s"
brew outdated
brew tap
php -v
which -a php
php --ini
nginx -v
curl --version
php --ri curl
~/.composer/vendor/laravel/valet/bin/ngrok version
ls -al ~/.ngrok2
brew info nginx
brew info php
brew info openssl
openssl version -a
openssl ciphers
sudo nginx -t
which -a php-fpm
/opt/homebrew/opt/php/sbin/php-fpm -v
sudo /opt/homebrew/opt/php/sbin/php-fpm -y /opt/homebrew/etc/php/8.0/php-fpm.conf --test
ls -al ~/Library/LaunchAgents | grep homebrew
ls -al /Library/LaunchAgents | grep homebrew
ls -al /Library/LaunchDaemons | grep homebrew
ls -aln /etc/resolv.conf
cat /etc/resolv.conf