Comment by speedgoose
4 hours ago
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.
4 hours ago
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.
It reads to me like chasing trends
That's the economy we've always been in. X is popular, if your company doesn't have a solution for X you're irrelevant.
that's all docker has been doing for years.
the tools and features certainly indicate so