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
TL;DR: I'm trying to use a EBS volume in an ECS service using the rexray/ebs driver but ECS is starting the task with the 'local' driver.
I'm trying to create a ecs service that will use an existing EBS volume as a means of persistent storage. The image is 'Ghost', an open source blogging service. It stores images and other media like themes in the folder /var/lib/ghost/content. I created an EBS volume named loop-content and set the ECS Tasks volume driver to rexray/ebs but the container still gets started with the local driver.
Just to be sure the rexray/ebs driver worked, I started up an ubuntu image and mapped the volume to /loop-content and it worked fined. All the data that was on the volume was now accessible on the running ubuntu container.
Just so we're clear, I've done all the setup to make rexray work on the container instance because I was able to mount the EBS volume onto the ubuntu docker container and access all the data on it.
georgeshanti
changed the title
[service] [request]: ECS creates local volume even though rexray/ebs is specified
ECS creates local volume even though rexray/ebs is specified
Aug 25, 2020
TL;DR: I'm trying to use a EBS volume in an ECS service using the
rexray/ebs
driver but ECS is starting the task with the 'local' driver.I'm trying to create a ecs service that will use an existing EBS volume as a means of persistent storage. The image is 'Ghost', an open source blogging service. It stores images and other media like themes in the folder
/var/lib/ghost/content
. I created an EBS volume namedloop-content
and set the ECS Tasks volume driver torexray/ebs
but the container still gets started with thelocal
driver.Just to be sure the
rexray/ebs
driver worked, I started up an ubuntu image and mapped the volume to/loop-content
and it worked fined. All the data that was on the volume was now accessible on the running ubuntu container.Just so we're clear, I've done all the setup to make rexray work on the container instance because I was able to mount the EBS volume onto the ubuntu docker container and access all the data on it.
The text was updated successfully, but these errors were encountered: