Support for Docker via WSL2?

[PhantomGamers]

I'm unsure if watchtower just doesn't work under WSL2 or if I'm doing something wrong.

Using the quick start docker create command to create the watchtower instance launches and says
time="2020-07-16T14:39:06Z" level=info msg="Starting Watchtower and scheduling first run: 2020-07-16 14:44:06 +0000 UTC m=+300.283507001"
However it never actually runs and the docker container doesn't restart properly after restarting windows (Docker reports that the container exited with code 255 but there are no errors in the log).

The only information in the log is the scheduling first run line above as well as time="2020-07-16T14:39:10Z" level=info msg="Waiting for running update to be finished..."

Seems that it never actually does anything.

I'm running Windows 10 Pro x64 build 2004 with Docker Desktop version 2.3.0.3 using the WSL 2 based engine. My other docker containers are working fine, watchtower is the only one I'm having problems with.

[github-actions[bot]]

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! 🙏

[piksel]

You can add --debug to get a bit more logging output. If there are no updated images, there is no additional output on info logging level.

Also; I just tried it inside WSL2, and it seems to operate normally.

[PhantomGamers]

With the --debug command I now see this output

time="2020-07-22T05:02:48Z" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized."

time="2020-07-22T05:02:49Z" level=debug msg="Retrieving running containers"

time="2020-07-22T05:02:49Z" level=debug msg="There are no additional watchtower containers"

time="2020-07-22T05:02:49Z" level=info msg="Starting Watchtower and scheduling first run: 2020-07-22 05:07:49 +0000 UTC m=+300.943165101"

time="2020-07-22T05:03:19Z" level=info msg="Waiting for running update to be finished..."

So it seems that the issue is that it's not able to see my other containers, though I'm still not sure why exactly it exits with code 255. This part only happens when the container is started with windows, when I manually start/restart it it stays running but with the same message stating that there are no additional watchtower containers.

All of my other containers are running and functional

[PhantomGamers]

Just to update this for anyone having a similar issue, I came across #583 and decided to try just putting all of my docker containers into a docker-compose file along with watchtower and it seems to be working now. Previously I was just using the docker create commands for each image.

[zoispag]

That's so good to hear! Thanks for the update and glad you found a working solution to your problem.