Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fargate Support #20

Open
backtrackbaba opened this issue Dec 18, 2017 · 3 comments · May be fixed by codesuki/ecs-gen#23
Open

Fargate Support #20

backtrackbaba opened this issue Dec 18, 2017 · 3 comments · May be fixed by codesuki/ecs-gen#23

Comments

@backtrackbaba
Copy link

Would this ECS nginx proxy work with Fargate too? I am trying to implement it on Fargate but I'm running into problems getting it started

@codesuki
Copy link
Owner

Any error messages? I haven't used Fargate, but it says it's based on ECS. Will check the docs when I find some time.

@davidworkman9
Copy link

Hi @codesuki, I'm trying to get this running with fargate as well. Everything is running, but the nginx proxy container logs InvalidParameterException: Container instance cannot be empty.. I've attached a role to my task with the permission: AmazonEC2ContainerServiceFullAccess

@davidworkman9
Copy link

davidworkman9 commented Dec 28, 2017

@digging into this, it appears that ecs.listContainerInstances returns an empty array when the cluster is backed by fargate instead of EC2.

EDIT: Tried running this in a cluster with a mix of fargate and EC2 services, still doesn't work but I get a different error message: container has no network bindings. skipping. It does correctly list containers running in EC2 mode in the output file.

More information - The above error message is because fargate seems to have a networkInterface instead of a networkBindings. Looks like the only need to extract that information is to get the port it's running on, I hardcoded port 80 and now I'm running into the fact that there isn't a ContainerInstanceArn on the task.

@davidworkman9 davidworkman9 linked a pull request Dec 28, 2017 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants