You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be related to #1050, but it is different somehow...
I get those errors:
time="2023-12-29T01:09:47Z" level=warning msg="Could not do a head request for \"bohdans/sungather:latest@sha256:bdbbc78f0ebf969e2e14dee01e39a72d9ddbde3d83f85cbb43bde29124e8a2d1\", falling back to regular pull." container=/hass_hass_solar1.1.p8t4wksigphc7wgkrvovalts0 image="bohdans/sungather:latest@sha256:bdbbc78f0ebf969e2e14dee01e39a72d9ddbde3d83f85cbb43bde29124e8a2d1"
time="2023-12-29T01:09:47Z" level=warning msg="Reason: Parsed container image ref has no tag: docker.io/bohdans/sungather@sha256:bdbbc78f0ebf969e2e14dee01e39a72d9ddbde3d83f85cbb43bde29124e8a2d1" container=/hass_hass_solar1.1.p8t4wksigphc7wgkrvovalts0 image="bohdans/sungather:latest@sha256:bdbbc78f0ebf969e2e14dee01e39a72d9ddbde3d83f85cbb43bde29124e8a2d1"
time="2023-12-29T01:09:52Z" level=warning msg="Could not do a head request for \"influxdb:1.8-alpine@sha256:d29e9e5a816afcc5ab2cc62f82e86b72089339a35d80dd9f72a0754343d30817\", falling back to regular pull." container=/hass_hass_influxdb.1.64ig4hplbpvrlnrrjzr9022vp image="influxdb:1.8-alpine@sha256:d29e9e5a816afcc5ab2cc62f82e86b72089339a35d80dd9f72a0754343d30817"
time="2023-12-29T01:09:52Z" level=warning msg="Reason: Parsed container image ref has no tag: docker.io/library/influxdb@sha256:d29e9e5a816afcc5ab2cc62f82e86b72089339a35d80dd9f72a0754343d30817" container=/hass_hass_influxdb.1.64ig4hplbpvrlnrrjzr9022vp image="influxdb:1.8-alpine@sha256:d29e9e5a816afcc5ab2cc62f82e86b72089339a35d80dd9f72a0754343d30817"
time="2023-12-29T01:10:04Z" level=warning msg="Could not do a head request for \"prom/node-exporter:latest@sha256:4cb2b9019f1757be8482419002cb7afe028fdba35d47958829e4cfeaf6246d80\", falling back to regular pull." container=/monitoring_node-exporter-2.1.c7kkv6wnzdw5yrxqcdu8nlx39 image="prom/node-exporter:latest@sha256:4cb2b9019f1757be8482419002cb7afe028fdba35d47958829e4cfeaf6246d80"
time="2023-12-29T01:10:04Z" level=warning msg="Reason: Parsed container image ref has no tag: docker.io/prom/node-exporter@sha256:4cb2b9019f1757be8482419002cb7afe028fdba35d47958829e4cfeaf6246d80" container=/monitoring_node-exporter-2.1.c7kkv6wnzdw5yrxqcdu8nlx39 image="prom/node-exporter:latest@sha256:4cb2b9019f1757be8482419002cb7afe028fdba35d47958829e4cfeaf6246d80"
[...]
however docker ps has got all information available:
$docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
26bdc57c2b18 bohdans/sungather:latest "python sungather.py…" About an hour ago Up About an hour hass_hass_solar1.1.p8t4wksigphc7wgkrvovalts0
ec41bb010c57 influxdb:alpine "/entrypoint.sh infl…" 2 days ago Up 2 days 8086/tcp monitoring_influxdb.1.nly6bfqourpytd6n6bcxiajx6
c8de88805b68 freshrss/freshrss:latest "./Docker/entrypoint…" 2 days ago Up 2 days 80/tcp freshrss_freshrss.1.lmc4makrget8curvn8tzglxa6
[...]
Steps to reproduce
docker run --rm --name watchtower --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower:latest --run-once
also
docker run --rm --name watchtower --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower:latest-dev --run-once
Expected behavior
I expect watchtower does what it supposed to.
Screenshots
No response
Environment
Docker Swarm
Docker version 24.0.7, build afdd53b
Your logs
as above
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏
Describe the bug
This may be related to #1050, but it is different somehow...
I get those errors:
however
docker ps
has got all information available:Steps to reproduce
also
Expected behavior
I expect watchtower does what it supposed to.
Screenshots
No response
Environment
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: