-
Controller Versionv5.15.24.19 Describe Your Issue or QuestionI've noticed this recently with your image and a couple maintainers of other projects. Whatever changes you're making daily or frequently is causing new images for the current release to be identified by watchtower, diun or manual pull. This never used to happen, so I found it strange when this started happening. Did something change with how releases/images are updated that's causing this? I have 5.15.24.19-amd64 pinned and it's still pulling in new images. Thanks! Expected BehaviorDon't publish changes that are not new releases. Steps to Reproducedocker compose pull How You're Launching the ContainerContainer LogsMongoDB LogsAdditional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
There are significant changes that I have been putting in over the last three days because TP-Link has released a beta v6 controller. As a part of that, I am upgrading the base image to a supported Ubuntu 24.04 and MongoDB 8. Due to how there are shared artifacts between the Dockerfile, install.sh, and entrypoints, the images are being rebuilt because of the automation. When there are vulnerabilities detected in the base images, that also triggers rebuilds but that has t really happened since May/June due to 20.04 going end of support. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the explanation. Appreciate you! |
Beta Was this translation helpful? Give feedback.
There are significant changes that I have been putting in over the last three days because TP-Link has released a beta v6 controller. As a part of that, I am upgrading the base image to a supported Ubuntu 24.04 and MongoDB 8. Due to how there are shared artifacts between the Dockerfile, install.sh, and entrypoints, the images are being rebuilt because of the automation.
When there are vulnerabilities detected in the base images, that also triggers rebuilds but that has t really happened since May/June due to 20.04 going end of support.