When several coding agents run the same app, Docker looks like the obvious answer: put every frontend in a container, put every API in a container, and put every worker in a container.
It works, but it adds friction. Stale images can serve old code, rebuilds slow down feedback, caches hide what actually changed, images and layers clutter storage, and debugging gains another runtime layer.
With one workspace, that may be fine. With several agents, it gets noisy fast.
Local isolation does not require containerizing every process
Most collisions come from ports, processes, Docker services, browser profiles, logs, and environment state. Agent-Up isolates those directly.
Your apps can still run normally using npm run dev, dotnet run, or ./gradlew bootRun.
Each workspace gets its own ports, and each process receives the full port map. Another agent gets a different range, which means no collisions and no full app image rebuilds.
Docker still has a clear role
Use Docker for databases, queues, caches, and object storage. Keep app code local, and keep infrastructure in Docker.
Let Agent-Up manage both as one workspace
✅ Git isolates the source.
✅ Agent-Up isolates the runtime.
✅ Docker isolates infrastructure.
Check out the open source repo
https://github.com/agent-up-oss/agent-up
Downloads
답글 남기기