We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The docker driver expects persistent storage to be a volume on the host machine so it can be mounted to the instance container.
The changes to docker-compose to use named volumes broke this.
Docker does now appear to support mounting sub-directories from named volumes, so this could be made to work.
See this SO answer for pointers to docker volume subpath work.
https://stackoverflow.com/a/38167198/504554
Will need to mandate current docker version.
Persistent storage to work with docker compose.
Install docker compose
I have provided an initial effort estimate
The text was updated successfully, but these errors were encountered:
I think this is going to need some significant changes to the driver-docker project.
It will need to switch mode to using HostConfig.Mounts rather than HostConfig.binds for the persistent volume
HostConfig.Mounts
HostConfig.binds
(arround line 108 in the docker.js file)
There are some possible hints here: apocas/dockerode#265 (comment)
I think it will need to include a VolumeOptions object
VolumeOptions
HostConfig: { Mounts: [ { Type: 'volume', Source: 'persistent-storeage', Target: '/data/storage', VolumeOptions: { Subpath: `${project.id}` } }, ],
This is just speculation, none of it has been tested.
Sorry, something went wrong.
ppawlowski
Successfully merging a pull request may close this issue.
Current Behavior
The docker driver expects persistent storage to be a volume on the host machine so it can be mounted to the instance container.
The changes to docker-compose to use named volumes broke this.
Docker does now appear to support mounting sub-directories from named volumes, so this could be made to work.
See this SO answer for pointers to docker volume subpath work.
https://stackoverflow.com/a/38167198/504554
Will need to mandate current docker version.
Expected Behavior
Persistent storage to work with docker compose.
Steps To Reproduce
Install docker compose
Prospects Affected:
Environment
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
The text was updated successfully, but these errors were encountered: