Share and learn in the Docker community.
I was excited about the --context support added in compose 1.26.0, but I immediately identified a problem:
--context
It appears that any volumes defined in the docker-compose.yml must be on the docker host, not the machine docker-compose is running on.
volumes
docker-compose.yml
docker-compose
Is my understanding correct?
Do you use any special volume driver that supports such a scenario? If not, be assured that you got it right. Context itself is just a switch for which api-endpoint to address. The api-endpoint is not involved in serving the content of volumes.
Nope, no special volume driver (assuming you mean this), thanks for clarification.
Aye, for instance a remote drive like sshfs, a remote cifs or nfs share all your machines can access, or something like this.