Watchtower: Downloading a new image every day

[kWAYTV]

Describe the problem/question

Watchtower every day is downloading a new image, and it's only happening with PrivateBin

Did you use the FAQ section?

• Yes, I have read the FAQ and I found no solution/answer there.

What you did?

1. Install Watchtower for unattended updates
2. Install PrivateBin
3. Wait for the notifications

What happens

No response

What should happen

No response

Additional information

No response

Server address

No response

Server OS

Ubuntu 24.04

Webserver

No response

PrivateBin version

latest

Browser and version

No response

Local operating system and version

No response

Issue reproducibility

No, I cannot reproduce it on https://privatebin.net.

[rugk]

Well the job is configured and supposed to run at midnight:
https://github.com/PrivateBin/docker-nginx-fpm-alpine/blob/93c095412f2c1f2e61ead9d3c714b1a26c0d7c42/.github/workflows/build-images.yml#L5

And it indeed pushes an image: https://github.com/PrivateBin/docker-nginx-fpm-alpine/pkgs/container/nginx-fpm-alpine

I guess the idea is it can pick up new upstream changes/builds, to fix security issues etc.

[kWAYTV]

Yeah but shouldn't be that done on trigger and not every midnight? since this is just flooding my server with unused docker images

IE: "v.X.X.X" tag release, on pr merge, on push

[elrido]

@kWAYTV, please have a look at the images' README.md, which explains the intent of the different tags offered:

Image tags

All images contain a release version of PrivateBin and are offered with the following tags:

• latest is an alias of the latest pushed image, usually the same as nightly, but excluding edge
• nightly is the latest released PrivateBin version on an upgraded Alpine release image, including the latest changes from the docker image repository
• edge is the latest released PrivateBin version on an upgraded Alpine edge image
• stable contains the latest PrivateBin release on the latest tagged release of the docker image git repository - gets updated when important security fixes are released for Alpine or upon new Alpine releases
• 1.5.1 contains PrivateBin version 1.5.1 on the latest tagged release of the docker image git repository - gets updated when important security fixes are released for Alpine or upon new Alpine releases, same as stable
• 1.5.1-... are provided for selecting specific, immutable images

So if you only want to get important updates, i.e. when there are security updates of the alpine base image or when we update an image to the latest alpine stable release, then pick a tag such as "2.0.0". You will then get to manually choose when to upgrade to the 2.0.1 release of our software, but still get updates of the image for the stack.

For reference, the "nightly" build got introduced upon community request.

Clearly there are different use cases and workflows and "latest" is therefore expected by the different user groups to behave in different ways and only one of these can be accommodated. When pushing "nightly" but not updating "latest", that got criticized as being inconsistent as well.

[kWAYTV]

@kWAYTV, please have a look at the images' README.md, which explains the intent of the different tags offered:

Image tags

All images contain a release version of PrivateBin and are offered with the following tags:

• latest is an alias of the latest pushed image, usually the same as nightly, but excluding edge

• nightly is the latest released PrivateBin version on an upgraded Alpine release image, including the latest changes from the docker image repository

• edge is the latest released PrivateBin version on an upgraded Alpine edge image

• stable contains the latest PrivateBin release on the latest tagged release of the docker image git repository - gets updated when important security fixes are released for Alpine or upon new Alpine releases

• 1.5.1 contains PrivateBin version 1.5.1 on the latest tagged release of the docker image git repository - gets updated when important security fixes are released for Alpine or upon new Alpine releases, same as stable

• 1.5.1-... are provided for selecting specific, immutable images

So if you only want to get important updates, i.e. when there are security updates of the alpine base image or when we update an image to the latest alpine stable release, then pick a tag such as "2.0.0". You will then get to manually choose when to upgrade to the 2.0.1 release of our software, but still get updates of the image for the stack.

For reference, the "nightly" build got introduced upon community request.

Clearly there are different use cases and workflows and "latest" is therefore expected by the different user groups to behave in different ways and only one of these can be accommodated. When pushing "nightly" but not updating "latest", that got criticized as being inconsistent as well.

Tysm, consider this solved