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 trying to bind mount a directory in a container that contains a colon in the path (like /a:b) using the long syntax, the creation of the container fails. docker compose up -d show following error message:
Error response from daemon: invalid volume specification: '/home/pi/a:b:/b:a:rw'
The same docker-compose.yaml works fine using docker compose version 2.29.7, but throws the error when using version 2.30.3 or 2.32.4
Unfortunately, even you're using the long syntax, we have to use the Docker Engine Bind API as the (more recent) Mount API is not strictly equivalent. This API requires we re-create the short syntax volume bind definition, and use of : makes it ambiguous.
This is an implementation detail and something we want to fix at some point (there are some blockers we need to address first) so documenting this would bring confusion (most users don't know engine has 2 APIs for the same purpose) and would depend on compose/engine version in use 🤨
As using colons in a path is uncommon corner-case, I prefer to close this issue as "not planned"
Description
When trying to bind mount a directory in a container that contains a colon in the path (like
/a:b
) using the long syntax, the creation of the container fails.docker compose up -d
show following error message:Error response from daemon: invalid volume specification: '/home/pi/a:b:/b:a:rw'
The same
docker-compose.yaml
works fine using docker compose version2.29.7
, but throws the error when using version2.30.3
or2.32.4
Steps To Reproduce
docker-compose.yaml
:docker compose up -d
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: