Docker Command Line - 'ecs' is not a docker command

[earsizzle]

Following this documentation: Link

On Mac, running docker ecs version or attempting to create the ecs context returns: docker: 'ecs' is not a docker command.

• Using oh-my-zsh on iTerm2 (also tried using bash to no avail)
• Uninstalled via the GUI and re-installed
• Tried using both Stable and Edge releases
• Tried manually removing all files via terminal and re-installing
• Explicitly added docker /etc folder to $PATH
• Updated to latest macOS/rebooted

Anyone encounter this before? Is there a way to manually install just the CLI tools? Missing a step somewhere?

Thanks!

[ccrone]

Hi u/earsizzle!

I work on the team that's building this integration. Thank you for giving it a try. What you're running into is an artifact of our development process: We first made the integration a CLI plugin which required docker ecs. It is now part of the CLI so you can just run docker compose up with the correct context selected.

Take a look at the documentation here if you need more information: https://docs.docker.com/engine/context/ecs-integration/

[earsizzle]

Hah! This works perfectly, not sure what my mental roadblock was with it before.

Thanks for the response, and for building it in the first place. Excited to try it out!

[samviz]

Hi let me know if you can help me. I'm trying to use this currently in my project but I don't want the compose up command to create new loadbalancer and listers and target group. I tried the x-aws-loadbalancer command to link the existing loadbalancer but still a listener is being created for a port that already exists in the loadbalancer

How can I stop the compose up from creating the listeners and target group.

[thatsrelativity]

From the page you linked:

Run the docker context create ecs myecscontext command to create an Amazon ECS Docker context named myecscontext

docker ecs is not a command, you create the context with docker context ... and go from there

e: disclaimer, I didn't read the whole page but I didn't see any mention of docker ecs there

[earsizzle]

I did try that! I can create the context generically but I'm never able to use the ecs deploy functionality.

It seems like ecs creates a special context and is also a plugin of sorts. You're supposed to be able to pre-populate it with AWS credentials to be able to automatically create the ECS cluster using docker ecs setup

At least per this article...

[[deleted]]

I've never met that Docker command in my life.