6 ms·

From within VSCode, you can run devcontainers, which bind mounts the project's directory into an isolated Docker container. Safe for --dangerously-skip-permissi

From within VSCode, you can run devcontainers, which bind mounts the project's directory into an isolated Docker container. Safe for --dangerously-skip-permissions https://code.visualstudio.com/docs/devcontainers/containers https://code.visualstudio.com/docs/devcontainers/containers

mbreese 9mo ago
As a note, running devcontainers in VSCode is easy, but not required. There is also a CLI tool that uses the same specifications. You can install it with brew or npm.
- pwagland 9mo ago
  I assume that you are talking about the [devcontainers LCI](https://github.com/devcontainers/cli https://github.com/devcontainers/cli) when you say "a CLI"?
  - mbreese 9mo ago
    Yes. I probably should have included the link. I stated using devcontainers through VSCode and find them incredibly helpful. It’s great for me to be able to load up exact coding environments on different computers. But, I only used them through VSCode. When I wanted to branch out a bit (and especially using coding agents), I started using the CLI version more. I find devcontainers a great way to work with different coding projects and wanted to make sure people knew that there was a way to use them outside of VSCode.
bugglebeetle 9mo ago
Tried this the other day and the setup on this is super cumbersome and requires you to constantly rebuild your entire dev and Claude Code environment every time you use a new container, including whitelisting URLs for package managers and the like.
- andrewmutz 9mo ago
  There are techniques to mitigate this. You can reuse containers instead of creating a new one each time. You can mount in directories (like ~/.claude) from your local machine so you dont have to set claude up each time.
  - raphinou 9mo ago
    I use agents in a container and persist their config like you suggest. After seeing some interest I shared my setup at https://github.com/asfaload/agents_container https://github.com/asfaload/agents_container It works fine for me on Linux.

mbreese 9mo ago

As a note, running devcontainers in VSCode is easy, but not required. There is also a CLI tool that uses the same specifications. You can install it with brew or npm.

pwagland 9mo ago
I assume that you are talking about the [devcontainers LCI](https://github.com/devcontainers/cli https://github.com/devcontainers/cli) when you say "a CLI"?
- mbreese 9mo ago
  Yes. I probably should have included the link. I stated using devcontainers through VSCode and find them incredibly helpful. It’s great for me to be able to load up exact coding environments on different computers. But, I only used them through VSCode. When I wanted to branch out a bit (and especially using coding agents), I started using the CLI version more. I find devcontainers a great way to work with different coding projects and wanted to make sure people knew that there was a way to use them outside of VSCode.

bugglebeetle 9mo ago

Tried this the other day and the setup on this is super cumbersome and requires you to constantly rebuild your entire dev and Claude Code environment every time you use a new container, including whitelisting URLs for package managers and the like.

andrewmutz 9mo ago
There are techniques to mitigate this. You can reuse containers instead of creating a new one each time. You can mount in directories (like ~/.claude) from your local machine so you dont have to set claude up each time.
- raphinou 9mo ago
  I use agents in a container and persist their config like you suggest. After seeing some interest I shared my setup at https://github.com/asfaload/agents_container https://github.com/asfaload/agents_container It works fine for me on Linux.