-
Notifications
You must be signed in to change notification settings - Fork 61
ebs-autoscale service stops cloud boothook init process #13
Comments
An update on this. It turns out that's with the The problem is that I need to create the mount before docker start to is as the container storage. I've tried another approach, inspired by your script, stopping the daemon, creating the mount, starting again docker and launching the ecs agent with
give up (for now) |
This looks like the following error: You need to add the
|
Nice. This solves the problem, thanks! I'm leaving the issue open because IMO it would be nice to have it working also in the boothook phase to avoid having to mess with docker and ecs agent stop/start. Feel free to proceed with how you think it's better. |
When provisioning an EC2 instance with this role executing as part of user-data, `update-route53.service` won't start because it has a dependency on `cloud-init.final` which has yet to exit, because the Ansible role needs to start the update-route53 service to complete. This is similar to this issue awslabs/amazon-ebs-autoscale#13
I have also run in to this issue. Im not sure what the consequence of starting the ecs agent before the end of my user data will be for my Batch node. |
I've noticed the ebs-autoscale service stops the Ec2 instance bootstrap when using the a GPU enabled instance. Note the last line in the instance log
To replicate the problem I've used to following userdata:
(I'm using a boot hook because I need to create the mount before the docker daemon is started)
Then I've launched as
It works fine with
ami-0501b08c7280e37c5
The text was updated successfully, but these errors were encountered: