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
external specifies that this volume already exists on the platform and its lifecycle is managed outside of that of the application. Compose doesn't then create the volume, and returns an error if the volume doesn't exist.
All other attributes apart from name are irrelevant. If Compose detects any other attribute, it rejects the Compose file as invalid.
In the example below, instead of attempting to create a volume called {project_name}_db-data, Compose looks for an existing volume simply called db-data and mounts it into the backend service's containers.
It's unclear what are the steps required on user's side to get an external volume to work (and get populated).
Where does it mount it from?
Can I just copy (or bind-mount) my data directly into to /var/lib/docker/volumes/db-data and expect it to work?
Is this a docs issue?
Type of issue
I can't find what I'm looking for
Description
In the https://docs.docker.com/compose/compose-file/07-volumes/ in volumes section for external it says:
It's unclear what are the steps required on user's side to get an external volume to work (and get populated).
Where does it mount it from?
Can I just copy (or bind-mount) my data directly into to
/var/lib/docker/volumes/db-data
and expect it to work?Location
https://docs.docker.com/compose/compose-file/07-volumes/
Suggestion
No response
The text was updated successfully, but these errors were encountered: