← Back to context

Comment by mplewis

4 hours ago

What does this have to do with Docker?

I guess people at Docker wanted to make an agent.

Having it docker branded, I could understand. It’s confusing but the docker brand is strong.

But exposing it as a docker subcommand is very confusing to me.

  • You don't really have to use the docker agent sub-command. docker-agent is a standalone binary. When it was created, though, 1.5 year ago, the idea was that it would be the docker compose for agents (original name was cagent, compose for agents).

    But it evolved differently and although it runs very well in docker containers and docker sandboxes, it also runs very well anywhere else.

Based on the repo short description and the first sentence of the readme:

It is called 'Docker' as the company, and it has nothing to do with the container technology.

Docker is rapidly fading into irrelevance now that they have missed their strategic acquisition interval via the Microsoft collab misstep, and now has to hype chase as fewer and fewer people believe in their long term viability as a company.

Great tech. Not a business.