Unable to update container to :latest via watchtower

[nitobuendia]

Describe the problem

When running watchtower to update cointainers, I get the following error:

Could not do a head request for "itzg/minecraft-server:latest", falling back to regular pull.
Reason: registry responded to head request with "404 Not Found", auth: "not present"

This did not happen before. The first occurence started on Jan 21st. It seems related to this issue. For example, pihole had the same error but they fixed it. The issue also contains links to instructions on how to solve it.

Container definition

This is my docker-compose.yaml file:

version: "3.3"

services:
  minecraft-server:
    image: itzg/minecraft-server
    container_name: minecraft-server
    restart: "no"
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      - TZ=Asia/Singapore
      - EULA=TRUE
      - VERSION=LATEST
      - MEMORY=4G
      # Change this to select the world you want to run.
      - LEVEL=world
    volumes:
      - "./data:/data"

Container logs

The container is running fine. This is not relevant for this issue.

[itzg]

Thanks for reporting and providing the background info.

Seems to have been introduced with https://github.com/docker/build-push-action/releases/tag/v3.3.0 and I'll disable the provenance.

IMHO this is a bug that Watchtower should fix rather than pushing the problem onto hundreds of image maintainers.

[itzg]

Image is building now https://github.com/itzg/docker-minecraft-server/actions/runs/3996953127

[itzg]

And it has been confirmed that this resolves issues that were seen with Azure deployments:

https://discord.com/channels/660567679458869252/660569641550217327/1067454634949611590

[nitobuendia]

Thanks for the quick fix. I can also confirm from my side it works!