Pushing new Images to DockerHub?
See original GitHub issueI noticed that the last commit to master was on March 25, however the image version on DockerHub is from February 11th.
As I want to make use of the new features, I was wondering when new images will be pushed?
Looking also at security patches (in particular those of nginx
and other software in the images like wget
) I am worried that they will not be applied to the images.
Judging from other comments (e.g. https://github.com/nginx-proxy/nginx-proxy/pull/1402#issuecomment-609408046, https://github.com/nginx-proxy/nginx-proxy/pull/1113#issuecomment-633775844) as well as issues #1304 and #1427 it seems that people have similar concerns. As a workaround (that works for me, but might not solve it for others) I have scheduled automated nightly builds of the master
branch on my server. I made an unofficial nginxproxy organization on DockerHub, and am pushing these images to nginxproxy/nginx-proxy.
If there is interest, I am happy to donate my server time to push to the official DockerHub repo or give other people access to the nginxproxy
organization.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7
nginx-proxy:0.8.0 is on dockerhub now.
@tkw1536 Thank you for your response. As I opened up my compose file I realised (oops!) that because I am using a 3 container setup from https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion I’m not directly using this container. But I have been following it to see what changes are being implemented. Thanks again, and I’ll need to now do more reading to try to understand how the new changes in this project are related to my setup.