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
When updating containers hosted on Docker with Windows (WSL2) watchtower claims that windows file paths (D:\Docker\configs\containerName:/config) are invalid. This method of referring to directories is otherwise supported by Docker, docker-compose and external tools using them like Portainer so I'm not sure why watchtower doesn't like it but I also have no idea what I'm doing 90% of the time in Docker anyway so I can't say.
Steps to reproduce
Install Docker Desktop on Windows and enable WSL2 mode.
Set up and launch an outdated container with a windows volume mount such as:
Open 'wsl' (I search wsl in the start menu and open the not tux icon. Should end up in a terminal interface logged into root@<device name>.
Execute docker run -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once.
Get normal output until time="<timestamp here>" level=error msg="Error response from daemon: invalid volume specification: '- D:\Docker\configs\containerName:/config:rw'".
Continue with update until output stating that container failed to update.
End up with container missing until remade externally (note that the image pull works fine so manually remaking the container will have it updated.
Expected behavior
The arguments that were used to create the container be used and work when watchtower remakes it.
Screenshots
No response
Environment
Windows 11 (10.0.22631 Build 22631)
WSL 2.4.10
64bit CPU
Docker Engine v27.5.1
Docker Desktop 4.38.0
Your logs
N/A
Additional context
I'm still feeling my way (blindly) around using Docker and using it under Windows is just a cruel and unusual punishment I've inflicted upon myself at this point so I'm probably missing a lot of information I should have here. If there's anything important I can provide please ask but I don't know how to create an outdated environment to test things with so any if I need to test things I'll need a basic explanation on how I can do so.
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
When updating containers hosted on Docker with Windows (WSL2) watchtower claims that windows file paths (
D:\Docker\configs\containerName:/config
) are invalid. This method of referring to directories is otherwise supported by Docker, docker-compose and external tools using them like Portainer so I'm not sure why watchtower doesn't like it but I also have no idea what I'm doing 90% of the time in Docker anyway so I can't say.Steps to reproduce
docker run -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once
.time="<timestamp here>" level=error msg="Error response from daemon: invalid volume specification: '- D:\Docker\configs\containerName:/config:rw'"
.Expected behavior
The arguments that were used to create the container be used and work when watchtower remakes it.
Screenshots
No response
Environment
Windows 11 (10.0.22631 Build 22631)
WSL 2.4.10
64bit CPU
Docker Engine v27.5.1
Docker Desktop 4.38.0
Your logs
Additional context
I'm still feeling my way (blindly) around using Docker and using it under Windows is just a cruel and unusual punishment I've inflicted upon myself at this point so I'm probably missing a lot of information I should have here. If there's anything important I can provide please ask but I don't know how to create an outdated environment to test things with so any if I need to test things I'll need a basic explanation on how I can do so.
The text was updated successfully, but these errors were encountered: