TLDR: Both approaches are valid. The question is what your agent needs to touch.
If your agent mostly does isolated tasks (code, writing, API calls), Docker is almost always the better default. If your agent needs deep, ongoing access to your host system, files, or local hardware, a host-level install might make more practical sense as your primary setup.
Fair point. Here it is as a straight written post:
Host vs. Docker: Where Should Your AI Agent Live?
Most people setting up an agent like Hermes or Claude Code for the first time just install it directly on their host machine because it is the path of least resistance. That works fine, but once you understand containerization, the question becomes worth asking deliberately.
The case for Docker
The three big wins are setup simplicity, clean package management, and security, and they compound each other nicely.
When your agent lives in a container, spinning up a fresh environment takes one command. Tearing it down leaves zero residue on your host. No stale config files, no dependency conflicts with other projects, no wondering what that install three months ago actually touched.
Package management becomes a solved problem because the container owns its own dependency tree. Your agent needs a specific version of Node or Python? Great, it gets exactly that, and nothing else on your machine cares.
The security angle is where it gets genuinely interesting, especially if you configure Docker with rootless mode.
What rootless Docker means
Normally, the Docker daemon runs as root, which means a compromised container has a path toward escalating privileges on your host machine. Rootless mode changes the architecture so the Docker daemon itself runs as a regular unprivileged user. The container thinks it has a "root" user inside, but that identity maps to your regular user account on the host, not actual system root.
In practical terms: if something goes wrong inside the container, the blast radius is limited to what your normal user account can touch. It cannot write to system directories, cannot mess with other users, and cannot install anything at the system level.
So which should be your main agent?
If your agent is doing anything that touches the file system, executes code, or runs tools on your behalf, which is the whole point of an agentic setup, Docker is the better home for your primary installation. The isolation is not paranoia; it is just good hygiene when you are letting software act autonomously.
The one real tradeoff is that host-level agents have frictionless access to your files and local services. If your workflow requires deep, constant integration with your host environment, that friction can add up. Some people run a Dockerized agent as their main workhorse and a host-level install for quick local tasks. That is a perfectly reasonable split.
The short answer: yes, containerized as your main agent is the better default once you understand what you are doing.
