-
Notifications
You must be signed in to change notification settings - Fork 314
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
Can't found? #44
Comments
Im having the same issue :( How to resolve this? |
A couple of systems on my end broke because of this. I fixed it by using I don't know if the "dockerfile" repository images were promoted to the top-level repository, or if I'm now using a different image from Docker's official repo, but it works perfectly fine anyway so I'll just continue to use it. |
Same here, and the other elasticsearch Docker is outdated. |
Many images in the "dockerfile" repository seem to have the same problem (look at issues in each github repo in https://github.com/dockerfile). Still waiting for an answer here though. |
so what happened to dockerfile? The /elasticsearch version is different |
My interpretation of @timini's URL — which lists docker pull registry.hub.docker.com/library/elasticsearch I replaced the Edit:
I tried also pulling: docker pull registry.hub.docker.com/elasticsearch This succeeds, but seems to be the same thing:
You can also pull from docker pull elasticsearch Which I believe leads you to
I think the error is just saying that the registry itself (i.e. Okay, this is the only one that didn't complain: docker pull library/elasticsearch Maybe it just consults a different Docker registry. ¯_(ツ)_/¯ |
The text was updated successfully, but these errors were encountered: