Docker with watchtower issue with update (buildx)

[stanthewizzard]

Steps to reproduce

Error 404 with watchtower for update of container

Expected behavior

update ok

Actual behavior

Hello

Apparently there is an issue with buildx

You should disable provenance as shown in docker/buildx#1513 (comment)

Thanks

Logs

No response

Komga version

latest

Operating system

docker

Other details

No response

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have checked the FAQ.
• I have updated the app to the latest version.
• I will fill out all of the requested information in this form.

[gotson]

i don't understand what's your problem, can you elaborate ?

[darthmooguy]

Oh, I'm getting this too in my watchtower pings. It looks like this:

I don't know why it does that, it only seems to have trouble with the Komga container.

[stanthewizzard]

A lot of container have the issue.
Could you follow the link in the first post ? Thank you thank you :))

name: Build and push
uses: docker/build-push-action@v3
with:
push: true
provenance: false
tags: user/app:latest

[gotson]

A lot of container have the issue.

then it's not a Komga issue.

[stanthewizzard]

Not directly. But it's the way komga docker is build

[gotson]

Not directly. But it's the way komga docker is build

Works for me so probably a you issue

[stanthewizzard]

There is issue for everyone of many docker containers (pi-hole for ex). Could you kindly go to the link at the beginning of the post ?

[gotson]

The link is about failing to push, but the push for Komga is working, so I don't unserstand how it's related?

[gotson]

containrrr/watchtower#1528 actually describes the issue. Images still get updated, but warnings are issued.

It's a watchtower issue, following a docker change. It's been fixed in containrrr/watchtower#1533

I don't think there's anything to be done here.

[stanthewizzard]

ok
thanks