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
Initially it seem to function as expected based on logs,
time="2023-03-07T19:00:24Z" level=info msg="Watchtower 1.5.3"
time="2023-03-07T19:00:24Z" level=info msg="Using no notifications"
time="2023-03-07T19:00:24Z" level=info msg="Only checking containers using enable label"
time="2023-03-07T19:00:24Z" level=info msg="Scheduling first run: 2023-03-07 20:00:24 +0000 UTC"
time="2023-03-07T19:00:24Z" level=info msg="Note that the first check will be performed in 59 minutes, 59 seconds"
time="2023-03-07T20:00:24Z" level=info msg="Found new hello_world_test:latest image (73c22c119cbe)"
time="2023-03-07T20:00:25Z" level=info msg="Stopping /hello_world_test (d711e4cf1ff6) with SIGTERM"
time="2023-03-07T20:00:49Z" level=info msg="Creating /hello_world_test"
but then it fails to create a new container after it detects the changed image
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
Running watchtower using Podman return error when a new container is created
Steps to reproduce
I was able to launch watchtower using Podman using command
podman run \ --detach \ --name watchtower \ --privileged \ --volume /run/user/${UID}/podman/podman.sock:/var/run/docker.sock:z \ --restart=on-failure:3 \ docker.io/containrrr/watchtower:latest \ --revive-stopped \ --cleanup \ --remove-volumes \ --label-enable \ --interval 3600
Initially it seem to function as expected based on logs,
but then it fails to create a new container after it detects the changed image
Expected behavior
My expectation is that container is created in the same way as using Docker.
Screenshots
No response
Environment
System:
Red Hat Enterprise Linux release 8.7 (Ootpa)
Podman:
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: