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
i use your plugin for ages and it works perfectly. Now, i need to deploy a Multicontainer to aws but i'm not able to do this. The Stack just failed with "Failed to launch environment." - that's it.
If i create the Environment with the same zip file via the beanstalk aws page, it works.
i created two service roles / iam
aws-elasticbeanstalk-ec2-role - with the Policy: AWSElasticBeanstalkMulticontainerDocker, AmazonEC2ContainerServiceforEC2Role
aws-elasticbeanstalk-service-role with the same Policies like aws-elasticbeanstalk-ec2-role
the console log from the instance don't show so much. i compared the cloud formation templates (one time from the mvn deploy and one time from the ElasticBeanstalk deploy via the webpage) and i don't see any important differences.
After checking all events, the only thing, wich one are different is that the mvn deployment not doing the ECS task
ECS task: arn:aws:ecs:eu-central-1:980585748732:task/b1098b24-d5ac-44e8-9987-e90e98fa0983 is RUNNING.
Starting new ECS task with awseb-Release-nebh2zbkfa:1.
Added instance [i-dd79c060] to your environment.
Hello,
i use your plugin for ages and it works perfectly. Now, i need to deploy a Multicontainer to aws but i'm not able to do this. The Stack just failed with "Failed to launch environment." - that's it.
If i create the Environment with the same zip file via the beanstalk aws page, it works.
i created two service roles / iam
aws-elasticbeanstalk-ec2-role - with the Policy: AWSElasticBeanstalkMulticontainerDocker, AmazonEC2ContainerServiceforEC2Role
aws-elasticbeanstalk-service-role with the same Policies like aws-elasticbeanstalk-ec2-role
My files are:
Dockerrun.aws.json
.ebextensions/blockdevice-sdh.config
.ebextensions/serviceroles.config
and some data from the pom.xml
the console log from the instance don't show so much. i compared the cloud formation templates (one time from the mvn deploy and one time from the ElasticBeanstalk deploy via the webpage) and i don't see any important differences.
After checking all events, the only thing, wich one are different is that the mvn deployment not doing the ECS task
The documentation from Elasticbeanstalk sayed, that EB take care of creating and running this automatically. http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_ecs.html
i hope you've some idea, why the container not starts.
Thanks a lot for you great work
Marcel
i guess, this is similar to #63
but my zip file looks like this (the name of Dockerrun.aws.json is exactly like it should be):
The text was updated successfully, but these errors were encountered: