Devcontainers

“fairly useless if you want to run a random tool like a linter on a random file(s)”

“As long as you install all the tools you need in it, it just works.”

“it seemed like a lot of complexity”

“It takes a bit of figuring out, but once set up the permission prompts go away”

“I quite like the 'features' layer system, adding extra tools to container in a declarative plugin-like way”

“Once you map your GitHub or AWS token into a container, it’s no longer useful as a security boundary.”

“super easy to setup with VSCode and ensures the AI can't access your main machine”

“gives me much needed flexibility and peace of mind with regards to data separation guarantees”

“it 2-for-1 also gives benefit of easy to setup coding env for people who don't care about ai”

“Devcontainers work without having to pass special arguments and deal with inconsistent stuff once in the devcontainer itself.”

“It's called devcontainers and there is a cli for managing it locally.”

“both for preventing agents losing your data and defending against secrets-harvesting supply-chain attacks”

“Use a .devcontainer and you're done in 10 seconds without any new runtime implementations.”

“This will limit the agent in what it can do in the system and what IPs/domains it can reach.”

“No need for any AI-specific tool, this is exactly what devcontainer is for!”

“With the devcontainer CLI, you can even use it from a terminal, no GUI/IDE required.”

“It's actually easier to do this than to not, since it provides reusable developer tooling that can be shared among all team members”

“given that it just wants full control of docker I'm guessing it takes none of that into consideration”

“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.”

“the vscode support for that is great and I don't really mind if it fucked up the ephemeral container”

“devcontainers let you completely containerize your development environment”

“run reproducible runtimes like k3s or devcontainers so environments stay consistent”

“They're very simple to setup and make using LLMs a lot more secure.”

“I only use devcontainers for this purpose, I'm not really a fan in general”

“having to craft containers with all my stuff sounds so painful”

“I also use devcontainers for the cli agents and that has also worked out well.”

“My one experience with dev containers put me off of dev containers”

“the development environment itself should be identical across everyone on the team”

“Devcontainers look perfect but also like a bit of a burden to entry with regards to setup.”

“it's pretty good but I occasionally came across dependencies that were difficult to install in containers”

“Much more usable than setting up a VM and you can share the same desktop environment as the host.”

“I find devcontainers a great way to work with different coding projects”

“If you’re working in docker-land or can use devcontainers, it just works”

“it gives me a persistent sandbox that have ports opened and work in any container environment”

“the worst thing that can happen is it deletes everything in the filesystem below the mounted repo”

“running this in a devcontainer[1][2] or as part of a CI system should be completely fine”

“you can just fire up the Ansible-provided Dev Container with all the dependencies”

“solutions like devcontainers or Nix's development shells can be useful even if costing more overhead”

“makes it easy to start working on random projects without installing a bunch of dependencies on the host computer”

“devpod and devcontainers and the whole system was the most joyous developer experience”