devcontainer

To set up a Docker dev container for Claude Code, you need a tailored .devcontainer configuration with a Dockerfile and devcontainer.json that pre-installs Claude Code and configures correct remote user permissions. This eliminates inconsistent development environment issues across machines. The configuration can be generated automatically by scanning project indicator files.

Yes, you can restrict network access for unattended Claude Code workflows by applying a secure firewall variant of your dev container configuration. This setup uses an optional firewall script to limit outbound network access strictly to whitelisted services, ensuring safe unattended operation without exposing the host network.

Automated dev container project detection works with Node.js, Python, Go, .NET, Rust, and Java by scanning for indicator files like package.json, requirements.txt, or .csproj. It automatically selects the correct base image, post-create commands, and technology-specific VS Code extensions for these project types.

The best way to update a dev container without losing custom configurations is to use an update-safe workflow that preserves user customizations. When regenerating devcontainer configs, the process retains your existing modifications while generating required files like the Dockerfile and devcontainer.json with pinned Claude Code versions.

Correct remote user permissions in a Docker development environment are required to prevent file ownership conflicts and ensure tools function properly inside the container. Generating a dev container with pre-configured remote users eliminates friction and broken builds caused by improper access rights.