You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: