Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connection refused while pulling images docker daemon in M1 Mac #239

Closed
nipun1999 opened this issue Mar 24, 2022 · 13 comments · Fixed by #251
Closed

connection refused while pulling images docker daemon in M1 Mac #239

nipun1999 opened this issue Mar 24, 2022 · 13 comments · Fixed by #251

Comments

@nipun1999
Copy link

Hi, I am facing the following issue while pulling any image after running colima with docker daemon
image

the docker daemon is successfully run and I can use docker ps and other standard commands. Please help

@daniel-arnauer
Copy link

same problem when using npm ci in Dockerfile.

Pinging google also does not work when running docker run busybox nslookup google.com

@rfay
Copy link
Contributor

rfay commented Mar 24, 2022

I've been working around this with colima start --dns=1.1.1.1 - that seems to solve the problem. I've had to colima stop and start from time to time.

colima version HEAD-3fc20b2
git commit: 3fc20b25c32b5a274fede77e52e8ae952b5393e6

runtime: docker
arch: aarch64
client: v20.10.13
server: v20.10.11

@abiosoft
Copy link
Owner

@nipun1999 can you install the current development version and give it a try brew install --HEAD colima?

@daniel-arnauer
Copy link

@abiosoft did not work for me but colima start --dns=1.1.1.1 did

@nipun1999
Copy link
Author

@rfay same error. I am on the same version as of yours and using the same arch
image

@abiosoft
Copy link
Owner

@nipun1999 are you behind a vpn connection?

@nipun1999
Copy link
Author

nope, I have disabled my VPN

@abiosoft
Copy link
Owner

@nipun1999 what is registry.docker-cn.com, is it a docker mirror somewhere? I am actually unable to pull from it.

@nipun1999
Copy link
Author

Not sure, I think this is picked automatically on the basis of DNS that I am passing. I changed the DNS to 8.8.8.8 and the URL is changed now
image

@nipun1999
Copy link
Author

you want me to do a fresh install ?

@abiosoft
Copy link
Owner

@nipun1999 do you get the same experience with the current release v0.3.4 as well?

@nipun1999
Copy link
Author

I think the current release was giving some problems in the ssh itself on M1 that's why I switched to HEAD.

@abiosoft abiosoft mentioned this issue Apr 1, 2022
@chriscasola
Copy link

I am having the same issue when running go get to download go modules, on M1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants