-
Notifications
You must be signed in to change notification settings - Fork 107
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
Warning: failed to get default registry endpoint from daemon #63
Comments
Cloud shell does not support docker commands and hence you cannot run any docker daemon related commands like |
I'm following the tutorial here. The Quicklab says that all actions can be done using the cloud shell but, to be fair, the tutorial doesn't make the same assertion. Maybe an update to the tutorial pages to warn people off Cloud Shell? |
Thanks for the notification on this, @rich-davies. As @sajayantony mentions, this isn't an ACR issue, per se, but rather part of a larger issue we're addressing on the documentation side. We’ve removed the Cloud Shell messaging from some articles which cannot be completed totally within the Cloud Shell, and are continuing to do so where it makes sense. I have a PR open in our documentation repo to address this issue. |
@rich-davies Hi Rich, we have added the following text to the first tutorial in both the ACS and ACI documentation sets. You can find it in the Before you begin section of both.
Please let us know if this resolves this issue, thanks. -MM |
ACS docs published. Closing for now. |
I have created a new Container Registry and, using the Cloud Shell, am unable to connect to it using az acr login --name .
I get the following message:
"Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
The text was updated successfully, but these errors were encountered: