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
Type: string
Required: no
The contents of the host parameter determine whether your data volume persists on the host container instance and where it is stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume, but the data is not guaranteed to persist after the containers associated with it stop running.
By default, Docker-managed volumes are created in /var/lib/docker/vfs/dir/. You can change this default location by writing OPTIONS="-g=/my/path/for/docker/volumes" to /etc/sysconfig/docker on the container instance.
sourcePath
Type: string
Required: no
The path on the host container instance that is presented to the container. If this parameter is empty, then the Docker daemon assigns a host path for you.
If the host parameter contains a sourcePath file location, then the data volume persists at the specified location on the host container instance until you delete it manually. If the sourcePath value does not exist on the host container instance, the Docker daemon creates it. If the location does exist, the contents of the source path folder are exported.
Maybe a little nitpicky but the naming doesn't line up well with theirs either.
Also not a huge deal in our specific case, I can just throw /tmp at it for now
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
May 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently:
Docs mentioning its behaviour when omitted:
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
Maybe a little nitpicky but the naming doesn't line up well with theirs either.
Also not a huge deal in our specific case, I can just throw /tmp at it for now
The text was updated successfully, but these errors were encountered: