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
The latest image on Docker Hub is already a few months old. With the current release process, new images are only build once a new release of Cottontail DB is tagged:
- 'v*'# Push events to matching v*, i.e. v1.0, v20.15.10
It is also not built when the Cottontail DB version remains the same, but the Dockerfile changes.
For production usage, it's important to have up to date images.
The image should be regularly rebuilt against its base image.
The best would be to rebuild whenever a new build of the base image is available or the Dockerfile changes.
This Action might be helpful, but be aware that there is not much activity on that repo.
A simple alternative would be to use a CronJob. IMHO at least once per month, after Patch Tuesday, should be sufficient.
The text was updated successfully, but these errors were encountered:
The latest image on Docker Hub is already a few months old. With the current release process, new images are only build once a new release of Cottontail DB is tagged:
cottontaildb/.github/workflows/release-docker.yml
Lines 2 to 5 in 33b9106
It is also not built when the Cottontail DB version remains the same, but the Dockerfile changes.
For production usage, it's important to have up to date images.
The image should be regularly rebuilt against its base image.
The best would be to rebuild whenever a new build of the base image is available or the Dockerfile changes.
This Action might be helpful, but be aware that there is not much activity on that repo.
A simple alternative would be to use a CronJob. IMHO at least once per month, after Patch Tuesday, should be sufficient.
The text was updated successfully, but these errors were encountered: