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

Please publish images to quay.io and public.ecr.aws / gallery.ecr.aws #1732

Open
nitrocode opened this issue Mar 29, 2023 · 3 comments · May be fixed by #1733
Open

Please publish images to quay.io and public.ecr.aws / gallery.ecr.aws #1732

nitrocode opened this issue Mar 29, 2023 · 3 comments · May be fixed by #1733

Comments

@nitrocode
Copy link

nitrocode commented Mar 29, 2023

Consul Template version

Not applicable

Configuration

Not applicable

Command

Not applicable

Debug output

Not applicable

Expected behavior

I'd like to pull images from quay.io and /or public.ecr.aws. This is because ecr pull through cache only supports these registries.

Actual behavior

I only see this image deployed to dockerhub which is unsupported by ecr pull through cache.

There are images on public.ecr.aws from hashicorp such as the hashicorp/consul-enterprise which is nice.

Steps to reproduce

Not applicable

References

How to publish to other repos

Image repos

Code reference

@nitrocode nitrocode changed the title Please publish to quay.io and public.ecr.aws / gallery.ecr.aws Please publish images to quay.io and public.ecr.aws / gallery.ecr.aws Mar 29, 2023
@nitrocode nitrocode linked a pull request Mar 29, 2023 that will close this issue
@nitrocode
Copy link
Author

cc: @roncodingenthusiast @eikenb

@forsberg
Copy link

forsberg commented Apr 4, 2024

Would also very much like to see consul-template on ECR public gallery, to avoid problems with Docker Hub pull request limit that hits one of my Kubernetes clusters from time to time.

Since a lot of hashicorp images are already on ECR public gallery, I imagine pushing this one as well can't be much work?

Please?

@nitrocode
Copy link
Author

They don't seem interested. I put in this PR #1733 in Oct 2023 and no response...

I uploaded it to the client's internal ECR which is the best solution until we have an AWS upstream image available.

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.

2 participants