[ ] I’m using docker compose setup, with modifications (modified .yml files, third party plugins/themes, etc.) - if so, describe your modifications in your post. Before reporting, see if your issue can be reproduced on the unmodified setup.
[ ] I’m not using docker on my primary instance, but my issue can be reproduced on the aforementioned docker setup and/or official demo.
Platform (i.e. Linux distro, Docker, PHP, PostgreSQL, etc) versions:
Synology NAS Docker
Hi
I use Watchtower and Whatsupdocker to notify of new releases/pull updates and from 25/12 I’m receiving a similar error for just cthulhoo/ttrss-web-nginx.
Just wondered whether this is a problem at my end or a problem brought about by this change
Watchtower started getting me similar messages around the same time. I am also using a Docker on a Synology NAS, but mine is a x86_64 based unit. I think I already confirmed that the image name did not change and the container does still update, so the message is more just an annoyance. I believe this is mainly a Watchtower issue.
time="2024-01-28T11:36:30-05:00" level=info msg="Watchtower 1.7.1"
time="2024-01-28T11:36:30-05:00" level=info msg="Using no notifications"
time="2024-01-28T11:36:30-05:00" level=info msg="Checking all containers (except explicitly disabled with label)"
time="2024-01-28T11:36:30-05:00" level=info msg="Running a one time update."
time="2024-01-28T11:36:33-05:00" level=warning msg="Could not do a head request for \"cthulhoo/ttrss-web-nginx:latest\", falling back to regular pull." container=/ttrss-web-nginx image="cthulhoo/ttrss-web-nginx:latest"
time="2024-01-28T11:36:33-05:00" level=warning msg="Reason: registry responded to head request with \"404 Not Found\", auth: \"not present\"" container=/ttrss-web-nginx image="cthulhoo/ttrss-web-nginx:latest"
time="2024-01-28T11:36:50-05:00" level=info msg="Session done" Failed=0 Scanned=24 Updated=0 notify=no
time="2024-01-28T11:36:50-05:00" level=info msg="Waiting for the notification goroutine to finish" notify=no
