I'm going to open that in a devcontainer
November 6, 2026 at 2:50 AM
I'm going to open that in a devcontainer
.node-versionを読むように出来ないか試し中
📦 New Pull Request: "fix(devcontainer): devcontainer の Node.js バージョンを更新"
https://github.com/misskey-dev/misskey/pull/18135
mi.osamu-storage.info
November 10, 2026 at 9:47 AM
.node-versionを読むように出来ないか試し中
You mean devcontainer? I'm using my own setup here:
pushin.eu/pjullrich/de...
But I heard that `enclave` is also cool:
enclave.eclipse.dev
pushin.eu/pjullrich/de...
But I heard that `enclave` is also cool:
enclave.eclipse.dev
pjullrich/devcontainer · Pushin.eu
A Claude-based Devcontainer for Elixir development
pushin.eu
November 3, 2026 at 5:00 PM
You mean devcontainer? I'm using my own setup here:
pushin.eu/pjullrich/de...
But I heard that `enclave` is also cool:
enclave.eclipse.dev
pushin.eu/pjullrich/de...
But I heard that `enclave` is also cool:
enclave.eclipse.dev
Mechanism-level defenses that actually work:
- pin extension versions, turn off auto-update
- run the agent in a container or devcontainer, not on your host
- keep prod credentials out of the environment the agent sees
- pin extension versions, turn off auto-update
- run the agent in a container or devcontainer, not on your host
- keep prod credentials out of the environment the agent sees
November 6, 2026 at 5:30 PM
Mechanism-level defenses that actually work:
- pin extension versions, turn off auto-update
- run the agent in a container or devcontainer, not on your host
- keep prod credentials out of the environment the agent sees
- pin extension versions, turn off auto-update
- run the agent in a container or devcontainer, not on your host
- keep prod credentials out of the environment the agent sees
Here's a quick tip for #Devcontainer users. By default, #VSCode auto-names containers with random strings—a total mess when managing ~25 active projects.
My new article shows 2 tricks to:
1. Custom-name your containers
2. Group containers from the same project together.
My new article shows 2 tricks to:
1. Custom-name your containers
2. Group containers from the same project together.
Devcontainer - Name Your Container and Group It in Docker Desktop | Christophe Avonture
Stop getting random container names like serene_ganguly from VS Code devcontainers; use runArgs to force a name and group containers in Docker Desktop.
www.avonture.be
November 5, 2026 at 1:06 PM
Here's a quick tip for #Devcontainer users. By default, #VSCode auto-names containers with random strings—a total mess when managing ~25 active projects.
My new article shows 2 tricks to:
1. Custom-name your containers
2. Group containers from the same project together.
My new article shows 2 tricks to:
1. Custom-name your containers
2. Group containers from the same project together.
New in zed-claude-devcontainer
1/ devc net lock: an outbound allowlist enforced from outside the container. With no NET_ADMIN/NET_RAW, even root inside can't undo it.
2/ Bring your own dotfiles via DEVC_DOTFILES_REPO.
3/ Optional headless IDA Pro […]
1/ devc net lock: an outbound allowlist enforced from outside the container. With no NET_ADMIN/NET_RAW, even root inside can't undo it.
2/ Bring your own dotfiles via DEVC_DOTFILES_REPO.
3/ Optional headless IDA Pro […]
Original post on infosec.exchange
infosec.exchange
November 10, 2026 at 9:20 PM
New in zed-claude-devcontainer
1/ devc net lock: an outbound allowlist enforced from outside the container. With no NET_ADMIN/NET_RAW, even root inside can't undo it.
2/ Bring your own dotfiles via DEVC_DOTFILES_REPO.
3/ Optional headless IDA Pro […]
1/ devc net lock: an outbound allowlist enforced from outside the container. With no NET_ADMIN/NET_RAW, even root inside can't undo it.
2/ Bring your own dotfiles via DEVC_DOTFILES_REPO.
3/ Optional headless IDA Pro […]
Remove renovate config `devcontainer` section (mjankowski)
https://github.com/mastodon/mastodon/pull/41462
https://github.com/mastodon/mastodon/pull/41462
Remove renovate config `devcontainer` section by mjankowski · Pull Request #41462 · mastodon/mastodon
The first two are part of the default list - https://docs.renovatebot.com/modules/manager/devcontainer/ - and the last one does not actually get maintained by renovate (it will update other deps wi...
github.com
November 4, 2026 at 9:47 AM
Remove renovate config `devcontainer` section (mjankowski)
https://github.com/mastodon/mastodon/pull/41462
https://github.com/mastodon/mastodon/pull/41462
I don't know why the preview in your video did not pick up the changes automatically - it most likely means that phoenix_live_reload doesn't work in your devcontainer, you can check if Phoenix logs a warning about the fs watcher on startup.
November 4, 2026 at 5:01 PM
I don't know why the preview in your video did not pick up the changes automatically - it most likely means that phoenix_live_reload doesn't work in your devcontainer, you can check if Phoenix logs a warning about the fs watcher on startup.
What kind of containers would they need? I’m running them inside a devcontainer which I’m spawning myself
November 4, 2026 at 7:32 AM
What kind of containers would they need? I’m running them inside a devcontainer which I’m spawning myself
I'm trying to switch from Zed to Herdr today and so far it's been pretty awesome. You can customize *everything*. I started by adding a bunch of mods and now I have Claude make them work for my setup where everything runs in a devcontainer. Herdr is a truly programmable editor, it seems.
November 2, 2026 at 4:12 PM
I'm trying to switch from Zed to Herdr today and so far it's been pretty awesome. You can customize *everything*. I started by adding a bunch of mods and now I have Claude make them work for my setup where everything runs in a devcontainer. Herdr is a truly programmable editor, it seems.
No I’m just running the agents directly inside the devcontainer which is a Debian docker container on my macOS host. I also have Postgres and minio containers running to which my app connects via a docker network. The agents themselves are not containers, just shells. Does that make it clearer?
November 4, 2026 at 4:15 PM
No I’m just running the agents directly inside the devcontainer which is a Debian docker container on my macOS host. I also have Postgres and minio containers running to which my app connects via a docker network. The agents themselves are not containers, just shells. Does that make it clearer?
再ビルドのたびにサインインし直しになる場合は、~/.claude を名前付きボリュームにマウントし、CLAUDE_CONFIG_DIR を同じパスに設定します。.claude.json もボリューム内に書かれるため、再ビルド後も設定が残ります。GitHub Codespaces でも同じ設定が必要です。
#ClaudeCode #DevContainer
#ClaudeCode #DevContainer
November 4, 2026 at 1:03 AM
再ビルドのたびにサインインし直しになる場合は、~/.claude を名前付きボリュームにマウントし、CLAUDE_CONFIG_DIR を同じパスに設定します。.claude.json もボリューム内に書かれるため、再ビルド後も設定が残ります。GitHub Codespaces でも同じ設定が必要です。
#ClaudeCode #DevContainer
#ClaudeCode #DevContainer
ソフトウェアの開発環境にも AI が入り込んできているけど、開発に使う環境と通常環境は分けておく必要を感じています。
私も自分の Github リポジトリでは雑に LLM 向けのプロンプトを書いてるけど（たとえば pull request についたコメントを読ませて、対応するとか）、これも「第三者がプロンプトインジェクションを狙ったコメントを書いた」場合には危ない。
個人で開発用にもう一台 PC 用意するのは大変なので、devcontainer を使ってアクセスできる範囲を制限しつつ、開発用のクレデンシャル（Github 用の SSH キーや、API キーなど）を分離するぐらいですかね。
私も自分の Github リポジトリでは雑に LLM 向けのプロンプトを書いてるけど（たとえば pull request についたコメントを読ませて、対応するとか）、これも「第三者がプロンプトインジェクションを狙ったコメントを書いた」場合には危ない。
個人で開発用にもう一台 PC 用意するのは大変なので、devcontainer を使ってアクセスできる範囲を制限しつつ、開発用のクレデンシャル（Github 用の SSH キーや、API キーなど）を分離するぐらいですかね。
November 5, 2026 at 2:31 AM
ソフトウェアの開発環境にも AI が入り込んできているけど、開発に使う環境と通常環境は分けておく必要を感じています。
私も自分の Github リポジトリでは雑に LLM 向けのプロンプトを書いてるけど（たとえば pull request についたコメントを読ませて、対応するとか）、これも「第三者がプロンプトインジェクションを狙ったコメントを書いた」場合には危ない。
個人で開発用にもう一台 PC 用意するのは大変なので、devcontainer を使ってアクセスできる範囲を制限しつつ、開発用のクレデンシャル（Github 用の SSH キーや、API キーなど）を分離するぐらいですかね。
私も自分の Github リポジトリでは雑に LLM 向けのプロンプトを書いてるけど（たとえば pull request についたコメントを読ませて、対応するとか）、これも「第三者がプロンプトインジェクションを狙ったコメントを書いた」場合には危ない。
個人で開発用にもう一台 PC 用意するのは大変なので、devcontainer を使ってアクセスできる範囲を制限しつつ、開発用のクレデンシャル（Github 用の SSH キーや、API キーなど）を分離するぐらいですかね。
The container's the easy half; egress is the hard one. Anthropic's devcontainer ships init-firewall.sh, iptables-whitelisting npm, GitHub and the API — without it skip-permissions lets injected text curl your env out. Is ~/.ssh mounted?
October 30, 2026 at 10:18 PM
The container's the easy half; egress is the hard one. Anthropic's devcontainer ships init-firewall.sh, iptables-whitelisting npm, GitHub and the API — without it skip-permissions lets injected text curl your env out. Is ~/.ssh mounted?
Twice in the span of a week I let a cli ai harness run on a Linux box to fix a devcontainer like the state using convicted criminals to build a jail
October 29, 2026 at 3:53 AM
Twice in the span of a week I let a cli ai harness run on a Linux box to fix a devcontainer like the state using convicted criminals to build a jail
However, if someone on your team uses rootful Docker, then your edited devcontainer.json will instead elevate the devcontainer execution context to host-level root. At best, this will make your workspace files unwritable from host. At worst, a supply chain attack is deadly at this point.
October 29, 2026 at 2:55 PM
However, if someone on your team uses rootful Docker, then your edited devcontainer.json will instead elevate the devcontainer execution context to host-level root. At best, this will make your workspace files unwritable from host. At worst, a supply chain attack is deadly at this point.
If you decide to switch to the rootless Docker mode, then your existing devcontainer setup will stop working. Specifically you won't be able to edit the files in the workspace from the container. That's because, in rootless mode, the container user is less privileged than your host user.
October 29, 2026 at 2:55 PM
If you decide to switch to the rootless Docker mode, then your existing devcontainer setup will stop working. Specifically you won't be able to edit the files in the workspace from the container. That's because, in rootless mode, the container user is less privileged than your host user.
If you want to run your agents "safer" locally, have a look at "enclave" which starts a docker image and restricts the agents to only the files and permissions you give it access to. A devcontainer, but in a nice CLI.
enclave.eclipse.dev
enclave.eclipse.dev
Eclipse Enclave: secure sandboxing for AI coding agents
Run AI coding agents at full autonomy inside isolated containers with network allowlists.
enclave.eclipse.dev
October 27, 2026 at 2:16 PM
If you want to run your agents "safer" locally, have a look at "enclave" which starts a docker image and restricts the agents to only the files and permissions you give it access to. A devcontainer, but in a nice CLI.
enclave.eclipse.dev
enclave.eclipse.dev
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
zenn.dev
October 25, 2026 at 10:34 PM
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
Claude Codeにghを使わせたいけど、GH_TOKENを環境変数に置きたくない人向けのdevcontainer構成。ghの実体を/usr/local/libに移してbinにラッパーを置き、Docker secretsのトークンをghプロセスにだけ渡す。エージェントがenvを覗いても何も出てこないのが肝。
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
October 26, 2026 at 9:19 AM
Claude Codeにghを使わせたいけど、GH_TOKENを環境変数に置きたくない人向けのdevcontainer構成。ghの実体を/usr/local/libに移してbinにラッパーを置き、Docker secretsのトークンをghプロセスにだけ渡す。エージェントがenvを覗いても何も出てこないのが肝。
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
#後で読む 用メモです→
Claude Codeにghを使わせてもGH_TOKENをコンテナの環境変数に置かないdevcontainer構成
Claude Codeにghを使わせてもGH_TOKENをコンテナの環境変数に置かないdevcontainer構成
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
zenn.dev
October 25, 2026 at 11:59 AM
#後で読む 用メモです→
Claude Codeにghを使わせてもGH_TOKENをコンテナの環境変数に置かないdevcontainer構成
Claude Codeにghを使わせてもGH_TOKENをコンテナの環境変数に置かないdevcontainer構成
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成 | hii-chi #zenn
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
zenn.dev
October 25, 2026 at 2:36 PM
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成 | hii-chi #zenn
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
https://zenn.dev/hii_chi/articles/claude-code-gh-token-wrapper
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
トークンを環境変数に置かず、コマンドを実行する瞬間だけ読み込む構成を紹介します。隠すことと読めなくすることは別だと注意しています。
秘密は値を書かず置き場所だけを残し、使う瞬間にだけ読んで必要なプロセスにだけ渡す形は、鍵や接続情報などあらゆる秘密の扱いに通じます。
トークンを環境変数に置かず、コマンドを実行する瞬間だけ読み込む構成を紹介します。隠すことと読めなくすることは別だと注意しています。
秘密は値を書かず置き場所だけを残し、使う瞬間にだけ読んで必要なプロセスにだけ渡す形は、鍵や接続情報などあらゆる秘密の扱いに通じます。
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
zenn.dev
October 26, 2026 at 1:48 AM
Claude Codeにghを使わせても、GH_TOKENをコンテナの環境変数に置かないdevcontainer構成
トークンを環境変数に置かず、コマンドを実行する瞬間だけ読み込む構成を紹介します。隠すことと読めなくすることは別だと注意しています。
秘密は値を書かず置き場所だけを残し、使う瞬間にだけ読んで必要なプロセスにだけ渡す形は、鍵や接続情報などあらゆる秘密の扱いに通じます。
トークンを環境変数に置かず、コマンドを実行する瞬間だけ読み込む構成を紹介します。隠すことと読めなくすることは別だと注意しています。
秘密は値を書かず置き場所だけを残し、使う瞬間にだけ読んで必要なプロセスにだけ渡す形は、鍵や接続情報などあらゆる秘密の扱いに通じます。
#後で読む 用メモです→
devcontainer で gedit を起動して mozc で日本語入力
devcontainer で gedit を起動して mozc で日本語入力
devcontainer で gedit を起動して mozc で日本語入力
zenn.dev
October 24, 2026 at 1:19 PM
#後で読む 用メモです→
devcontainer で gedit を起動して mozc で日本語入力
devcontainer で gedit を起動して mozc で日本語入力