# Devcontainers

66 Hacker News commenters recommended Devcontainers and 13 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months. It meets the Hacker Approved badge rule.

**Verdict:** Recommended for reproducible, isolated team development environments and keeping AI agents off the host, though setup effort is the common caveat.

## Why people recommend it

- Limits damage from AI agents (6 comments): "Wherever practical, I also recommend using devcontainers, so that in addition to breaking supply chain security, large-scale damage would require an unpatched sandbox exploit too." ([source](https://news.ycombinator.com/item?id=47523154)) "both for preventing agents losing your data and defending against secrets-harvesting supply-chain attacks" ([source](https://news.ycombinator.com/item?id=48353212)) "the worst thing that can happen is it deletes everything in the filesystem below the mounted repo" ([source](https://news.ycombinator.com/item?id=46559090))
- Keeps host machine clean (3 comments): "makes it easy to start working on random projects without installing a bunch of dependencies on the host computer" ([source](https://news.ycombinator.com/item?id=46282340)) "super easy to setup with VSCode and ensures the AI can't access your main machine" ([source](https://news.ycombinator.com/item?id=48901424)) "devcontainers let you completely containerize your development environment" ([source](https://news.ycombinator.com/item?id=47316688))
- Consistent, shareable team environments (4 comments): "It's actually easier to do this than to not, since it provides reusable developer tooling that can be shared among all team members" ([source](https://news.ycombinator.com/item?id=47686660)) "Devcontainers work without having to pass special arguments and deal with inconsistent stuff once in the devcontainer itself." ([source](https://news.ycombinator.com/item?id=48767994)) "run reproducible runtimes like k3s or devcontainers so environments stay consistent" ([source](https://news.ycombinator.com/item?id=47295553))
- Easy setup that just works (4 comments): "it 2-for-1 also gives benefit of easy to setup coding env for people who don't care about ai" ([source](https://news.ycombinator.com/item?id=48896404)) "Use a .devcontainer and you're done in 10 seconds without any new runtime implementations." ([source](https://news.ycombinator.com/item?id=48246060)) "If you’re working in docker-land or can use devcontainers, it just works" ([source](https://news.ycombinator.com/item?id=46568642))

## What people warn about

- Hard setup and configuration (4 comments): "Devcontainers look perfect but also like a bit of a burden to entry with regards to setup." ([source](https://news.ycombinator.com/item?id=46694405)) "My one experience with dev containers put me off of dev containers" ([source](https://news.ycombinator.com/item?id=46736053)) "having to craft containers with all my stuff sounds so painful" ([source](https://news.ycombinator.com/item?id=46876406))
- Container doesn't protect credentials (2 comments): "Once you map your GitHub or AWS token into a container, it’s no longer useful as a security boundary." ([source](https://news.ycombinator.com/item?id=49176822)) "given that it just wants full control of docker I'm guessing it takes none of that into consideration" ([source](https://news.ycombinator.com/item?id=47616866))

## Cite as

Hacker Approved, "Devcontainers", https://hackerapproved.com/p/devcontainers/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).