Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] "Could not do a head request" using Watchtower for automated Docker update #1192

Closed
3 tasks done
djkynch opened this issue Apr 5, 2023 · 3 comments
Closed
3 tasks done
Labels
wontfix This will not be worked on

Comments

@djkynch
Copy link

djkynch commented Apr 5, 2023

Description

Getting an error when using Watchtower:

level=warning msg="Could not do a head request for \"ghcr.io/benphelps/homepage:latest\", falling back to regular pull." container=/homepage image="ghcr.io/benphelps/homepage:latest"
level=warning msg="Reason: registry responded to head request with \"404 Not Found\", auth: \"not present\"" container=/homepage image="ghcr.io/benphelps/homepage:latest"

Steps to reproduce

Added homepage docker container via docker-compose and watched with Watchtower.

homepage version

v0.6.14 (a0fa636, Apr 5, 2023)

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Other

This was apparently discussed here.

There is a resolution surrounding docker buildx.

Before submitting, I have made sure to

@djkynch djkynch added the bug Something isn't working label Apr 5, 2023
@shamoon shamoon closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2023
@shamoon
Copy link
Collaborator

shamoon commented Apr 5, 2023

You can use the setting noted in that linked issue, the new manifest will be supported eventually. Also, this is a warning...

@shamoon shamoon added wontfix This will not be worked on and removed bug Something isn't working labels Apr 5, 2023
@kimpenhaus
Copy link
Contributor

kimpenhaus commented Apr 5, 2023

@djkynch that was fixed with release 1.5.2 and PR 1533

Copy link
Contributor

github-actions bot commented Feb 5, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants