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

nginx image is not being tracked by renovate #105

Open
noahpb opened this issue Sep 17, 2024 · 2 comments
Open

nginx image is not being tracked by renovate #105

noahpb opened this issue Sep 17, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@noahpb
Copy link

noahpb commented Sep 17, 2024

It appears that the nginx image used in this project was mirrored to our ghcr as a one-time workaround for public Dockerhub rate limiting. The image is now two minor versions behind.

We should create a long-term plan for keeping this image up to date. Perhaps creating an automated build pipeline or using a "unicorn" flavor of this image is a viable solution. The end result should include the usage of an nginx image that is regularly udpated and renovate should be configured to track updates.

@noahpb noahpb added the enhancement New feature or request label Sep 17, 2024
@noahpb
Copy link
Author

noahpb commented Sep 17, 2024

Just saw @mjnagel's branch nginx-update. This should satisfy the issue.

@mjnagel
Copy link
Contributor

mjnagel commented Sep 17, 2024

Was just typing a comment on here - I think using Chainguard's latest + pinning to a sha is a smart path forward. I think I encountered some issues with that update though - possibly due to missing binaries in the chainguard image if I remember right? I didn't have enough time to poke at that more - but if that is truly a problem we could probably make a pipeline to mirror images here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants