Skip to content
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

Open
lucabelluccini opened this issue Jan 14, 2025 · 6 comments
Open

Release images on Docker Hub instead of just docker.elastic.co #1270

lucabelluccini opened this issue Jan 14, 2025 · 6 comments
Labels
Team:Ecosystem Label for the Packages Ecosystem team

Comments

@lucabelluccini
Copy link

As per title, it would be interesting to have the EPR images published to hub.docker.com/u/elastic

@lucabelluccini
Copy link
Author

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.
Can we track this item for prioritization?

@kpollich
Copy link
Member

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 docker push to another location, or will we need more complexity around credentials/auth, etc?

@kpollich kpollich added the Team:Ecosystem Label for the Packages Ecosystem team label Jan 15, 2025
@jsoriano
Copy link
Member

Is this simply a matter of updating CI jobs to docker push to another location, or will we need more complexity around credentials/auth, etc?

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.

@IanLee1521
Copy link

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 8.17.* tags are out yet). If this isn't the right place to report issues with docker.elastic.co I'm happy to bring the conversation to the right place.

@mrodm
Copy link
Contributor

mrodm commented Feb 13, 2025

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.

Looking into this, it looks like it is related to this PR: elastic/fleet-server#4433
That removed the required settings to trigger buildkite builds when some specific tags are pushed.

@mrodm
Copy link
Contributor

mrodm commented Feb 13, 2025

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.

Looking into this, it looks like it is related to this PR: elastic/fleet-server#4433 That removed the required settings to trigger buildkite builds when some specific tags are pushed.

@IanLee1521 docker image for 8.17.2 (docker.elastic.co/package-registry/distribution:8.17.2) is available now, thanks for the heads up!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Team:Ecosystem Label for the Packages Ecosystem team
Projects
None yet
Development

No branches or pull requests

5 participants