Open siddarthsreeni-zz opened 6 years ago
Shared data volumes are for sharing data between containers within an instance of a running task. Since the CLI really only supports one container running per task, there's not much utility in defining volumes today. What did you have in mind in terms of using volumes via the CLI?
I was looking through the json and we could specify a shared data volume. Like a shared file etc. This could help save producer consumer related problems by using the volume as a semaphore etc. I had been trying to implement such a service instead. If a data volume could be specified like --data-volume whole running fargate clusters would be so much helpful in many situations.
Yea I agree it's one container per task. But multiple tasks can be run, which would all try to access the same shared data volume.
Gotcha. Yeah, shared data volumes are actually only accessible within a given task, not throughout an entire cluster. If AWS Fargate ships a feature to allow persistence across an entire cluster, I'll certainly immediately support it. Until then, I think this proposal is blocked.
Thanks. This isn’t usable today on AWS Fargate as neither privileged node nor host container paths are supported.
On Sun, Feb 18, 2018 at 5:35 PM Luis Gustavo notifications@github.com wrote:
https://github.com/rog555/aws_batch_efs
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/jpignata/fargate/issues/30#issuecomment-366554335, or mute the thread https://github.com/notifications/unsubscribe-auth/AABNPzgTLOMYjpw_A4tti3oPeZWwxMTYks5tWKWngaJpZM4R8Mtg .
@jpignata This seems to exist https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-storage.html
I was looking forward to share data volumes between the fargate cluster. So far I've been able to find this, but have you tried to employ the same on your fargate-cli.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_data_volumes.html