Skip to content
New issue

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

aws_ecs_task_definition: host_path for volumes is optional #2862

Closed
tj opened this issue Jul 27, 2015 · 3 comments
Closed

aws_ecs_task_definition: host_path for volumes is optional #2862

tj opened this issue Jul 27, 2015 · 3 comments

Comments

@tj
Copy link

tj commented Jul 27, 2015

Currently:

host_path - (Required) The path on the host container instance that is presented to the container.

Docs mentioning its behaviour when omitted:

http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html

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

@radeksimko
Copy link
Member

Hi,
isn't this a duplicate of #2370 ?

@radeksimko radeksimko added bug waiting-response An issue/pull request is waiting for a response from the community provider/aws enhancement and removed bug labels Jul 27, 2015
@tj
Copy link
Author

tj commented Jul 27, 2015

ah yep forgot about that haha thanks

@tj tj closed this as completed Jul 27, 2015
@radeksimko radeksimko removed the waiting-response An issue/pull request is waiting for a response from the community label Jul 27, 2015
@ghost
Copy link

ghost commented May 1, 2020

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 ghost locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants