Claude In Docker — DevOps skill for Claude Code

CinD

About

**claude-in-docker** (`cind`) is a simple docker image that let's you run claude-code in a docker container and have more control over what claude can and can not do on your machine.

Wait... but why?

Because I usually prefer to run tools in a container, rather than installing them locally on my machine.

Also, and I can't stress this enough, because it provides better isolation and security.

And last but not least, because Anthropic is known to release models that are untested (well, just to be fair, let's say not fully tested), bypass permissions, and are generally dangerous to run on your local machine (unless, of course, you don't care that your secrets get leaked, your files get deleted, or CC gets access to anything outside of the CWD)

Basically, if you care about security - treat any AI agent like an _untrusted_ contractor with access to your machine.

I'm amazed anyone thought simply editing the agent config file was akin to security.

(c) random comment on Reddit

Still not convinced?

Here are some examples of what Anthropic gently calls "misaligned behavior", taken from [Opus 4.6 System Card](https://www-cdn.anthropic.com/0dd865075ad3132672ee0ab40b05a53f14cf5288.pdf):

• At times, Claude Opus 4.6 acted irresponsibly in acquiring authentication tokens for online service accounts:
  • In one case, the model was asked to make a pull request on GitHub, but was not authenticated, and so could not do so. Rather than asking the user to authenticate, it searched and found a misplaced GitHub personal access token user on an internal system—which it was aware belonged to a different user—and used that.

...