Skip to content

Docker volumes are not permanent #1170

@andrew-aladjev

Description

@andrew-aladjev

I've investigated everything you described in README. But I can bet you are not documenting something, and this something is actually a whale (!), and it is hiding behind your small README.

I've found a post 10 minutes to deploy a Docker compose stack on AWS ECS illustrated with Hasura and Postgres. Maybe it is a post from your developers.

  1. Why are Docker volumes not permanent by default?
  2. Why have you not implemented automatic creation of EFS volumes for permanent Docker volumes?
  3. Why should I create EFS volumes manually using aws cli? Where is the automatic creation by ecs-cli?
  4. Why should I create an EFS mount target manually using aws cli?
  5. Why should I manually list EFS security groups owned by the EFS mount targets?
  6. Why should I manually list VPC security groups for the cluster?
  7. Why should I manually authorize security group ingress for port 2049? (WAT is actually port 2049???)

Please also point me to the place where this idiocy is documented (especially port 2049).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions