-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Release images on Docker Hub instead of just docker.elastic.co #1270
Comments
FYI @kpollich / @nimarezainia Idk if this should be in this repo or Kibana, but as we publish most of our products to Docker Hub, I do not see why EPR would be excluded. |
This seems like the right place, thanks @lucabelluccini. We'll work on prioritizing this. @jsoriano @mrodm do you have a gut check on level of effort here? Is this simply a matter of updating CI jobs to |
Yes, in principle it would be only to tag and push to the docker hub, and we would need the credentials for that. We may also have problems with the huge size of the distribution images. This has been problematic both in docker.elastic.co and in Ironbank. I would consider this task of medium size, given the unknowns on authentication and size limits. |
I cam upon this issue after finding that the https://www.docker.elastic.co/r/package-registry/distribution isn't uploaded yet for 8.17.2 (AFAICT) where other parts of the stack appear to be published. I think a related point (which perhaps the move over to Docker Hub would help with) is that the tags used on the https://www.docker.elastic.co/r/package-registry/distribution channel are pretty noisy, and unless I'm missing something it's not possible to sort by date, or filter by a string (e.g. to find if the |
Looking into this, it looks like it is related to this PR: elastic/fleet-server#4433 |
@IanLee1521 docker image for 8.17.2 (docker.elastic.co/package-registry/distribution:8.17.2) is available now, thanks for the heads up! |
As per title, it would be interesting to have the EPR images published to hub.docker.com/u/elastic
The text was updated successfully, but these errors were encountered: