Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows file path incompatibility #2077

Open
C4J3 opened this issue Feb 7, 2025 · 1 comment
Open

Windows file path incompatibility #2077

C4J3 opened this issue Feb 7, 2025 · 1 comment

Comments

@C4J3
Copy link

C4J3 commented Feb 7, 2025

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

  1. Install Docker Desktop on Windows and enable WSL2 mode.
  2. Set up and launch an outdated container with a windows volume mount such as:
...
volumes:
   - D:\Docker\configs\containerName:/config
...
  1. 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>.
  2. Execute docker run -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once.
  3. Get normal output until time="<timestamp here>" level=error msg="Error response from daemon: invalid volume specification: '- D:\Docker\configs\containerName:/config:rw'".
  4. Continue with update until output stating that container failed to update.
  5. 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.

Copy link

github-actions bot commented Feb 7, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant