I _was_ running it in devcontainers, but then I started using orca... and then I kept needing to rebuild the container because of ruby updates...
But I'm also happy with lots of permission interruptions. I don't trust long-running tasks.
I now know that I would be a micromanager.
But I'm also happy with lots of permission interruptions. I don't trust long-running tasks.
I now know that I would be a micromanager.
November 11, 2026 at 6:10 PM
I _was_ running it in devcontainers, but then I started using orca... and then I kept needing to rebuild the container because of ruby updates...
But I'm also happy with lots of permission interruptions. I don't trust long-running tasks.
I now know that I would be a micromanager.
But I'm also happy with lots of permission interruptions. I don't trust long-running tasks.
I now know that I would be a micromanager.
@nicoverbruggen.be Sorry to message out of the blue, but I found your article on ditching Win for Bazzite.
Could I ask how you're doing dev work on it?
Many of the toolchains I use are PATH based and not working well in Distrobox or causing me literal (burnout) headaches in devcontainers.
Any tips?
Could I ask how you're doing dev work on it?
Many of the toolchains I use are PATH based and not working well in Distrobox or causing me literal (burnout) headaches in devcontainers.
Any tips?
November 8, 2026 at 11:36 AM
@nicoverbruggen.be Sorry to message out of the blue, but I found your article on ditching Win for Bazzite.
Could I ask how you're doing dev work on it?
Many of the toolchains I use are PATH based and not working well in Distrobox or causing me literal (burnout) headaches in devcontainers.
Any tips?
Could I ask how you're doing dev work on it?
Many of the toolchains I use are PATH based and not working well in Distrobox or causing me literal (burnout) headaches in devcontainers.
Any tips?
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.
We feel like Dev Containers are a gift to developers, allowing us to work with a variety of programming languages and tools without messing up the base system.
Learn more about Dev Containers in this webinar: https://youtube.com/live/Wvetp2YkwPY
#DevContainers
Learn more about Dev Containers in this webinar: https://youtube.com/live/Wvetp2YkwPY
#DevContainers
October 31, 2026 at 12:30 PM
We feel like Dev Containers are a gift to developers, allowing us to work with a variety of programming languages and tools without messing up the base system.
Learn more about Dev Containers in this webinar: https://youtube.com/live/Wvetp2YkwPY
#DevContainers
Learn more about Dev Containers in this webinar: https://youtube.com/live/Wvetp2YkwPY
#DevContainers
How do you keep dev environments aligned across laptop, cloud & CI?
At #PSConfEU, @chagercoc.bsky.social shows how #DevContainers:
✅ Remove setup issues
✅ Standardise environments
✅ Speed up onboarding
👉 youtu.be/jsp1mZVhDzQ?si=WYP...
#PowerShell #automation #IT #DevOps #Conference
At #PSConfEU, @chagercoc.bsky.social shows how #DevContainers:
✅ Remove setup issues
✅ Standardise environments
✅ Speed up onboarding
👉 youtu.be/jsp1mZVhDzQ?si=WYP...
#PowerShell #automation #IT #DevOps #Conference
- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
youtu.be
October 30, 2026 at 2:00 PM
How do you keep dev environments aligned across laptop, cloud & CI?
At #PSConfEU, @chagercoc.bsky.social shows how #DevContainers:
✅ Remove setup issues
✅ Standardise environments
✅ Speed up onboarding
👉 youtu.be/jsp1mZVhDzQ?si=WYP...
#PowerShell #automation #IT #DevOps #Conference
At #PSConfEU, @chagercoc.bsky.social shows how #DevContainers:
✅ Remove setup issues
✅ Standardise environments
✅ Speed up onboarding
👉 youtu.be/jsp1mZVhDzQ?si=WYP...
#PowerShell #automation #IT #DevOps #Conference
DevContainers is a wonderful feature: you define your environment once and it's reproduced for all your collaborators. And provides *some* security against supply chain attacks.
The downside is that it locks you down to one engine (Docker, Docker Rootless, Podman) and assumes everyone will use it.
The downside is that it locks you down to one engine (Docker, Docker Rootless, Podman) and assumes everyone will use it.
October 29, 2026 at 2:55 PM
DevContainers is a wonderful feature: you define your environment once and it's reproduced for all your collaborators. And provides *some* security against supply chain attacks.
The downside is that it locks you down to one engine (Docker, Docker Rootless, Podman) and assumes everyone will use it.
The downside is that it locks you down to one engine (Docker, Docker Rootless, Podman) and assumes everyone will use it.
Spent a full day getting devcontainers to work with my custom nvim/lazyvim, gpg, and git over ssh lol
October 23, 2026 at 3:49 PM
Spent a full day getting devcontainers to work with my custom nvim/lazyvim, gpg, and git over ssh lol
so devcontainers really haven't worked out, have they? I went to a talk about devcontainers at Kubecon years ago and the idea seemed neat, but now I'm trying to use one and discovering that there seems to be no supported tooling besides VSCode and Docker? and even that seems pretty creaky […]
Original post on hachyderm.io
hachyderm.io
October 22, 2026 at 4:48 AM
so devcontainers really haven't worked out, have they? I went to a talk about devcontainers at Kubecon years ago and the idea seemed neat, but now I'm trying to use one and discovering that there seems to be no supported tooling besides VSCode and Docker? and even that seems pretty creaky […]
@jbcrawford
The cases where I've seen devcontainers in active use seem fairly trivial, like it wasn't needed at all. Unfortunately, way too much software today has development envrionment setup instructions like "Use this Dockerfile and Docker Swarm config file" or equivalent kubernetes config […]
The cases where I've seen devcontainers in active use seem fairly trivial, like it wasn't needed at all. Unfortunately, way too much software today has development envrionment setup instructions like "Use this Dockerfile and Docker Swarm config file" or equivalent kubernetes config […]
Original post on mindly.social
mindly.social
October 22, 2026 at 6:31 AM
@jbcrawford
The cases where I've seen devcontainers in active use seem fairly trivial, like it wasn't needed at all. Unfortunately, way too much software today has development envrionment setup instructions like "Use this Dockerfile and Docker Swarm config file" or equivalent kubernetes config […]
The cases where I've seen devcontainers in active use seem fairly trivial, like it wasn't needed at all. Unfortunately, way too much software today has development envrionment setup instructions like "Use this Dockerfile and Docker Swarm config file" or equivalent kubernetes config […]
Oracle JDK runtimes hide in your Dockerfiles, CI workflows (setup-java distribution: 'oracle'), Gradle toolchains and devcontainers — under Oracle's paid license terms. This VS Code extension finds each Java runtime and…
https://getreadystack.com/tools/oracle-jdk-license-gate?ref=bs_readystac
https://getreadystack.com/tools/oracle-jdk-license-gate?ref=bs_readystac
October 12, 2026 at 7:31 AM
Oracle JDK runtimes hide in your Dockerfiles, CI workflows (setup-java distribution: 'oracle'), Gradle toolchains and devcontainers — under Oracle's paid license terms. This VS Code extension finds each Java runtime and…
https://getreadystack.com/tools/oracle-jdk-license-gate?ref=bs_readystac
https://getreadystack.com/tools/oracle-jdk-license-gate?ref=bs_readystac
my solution so far is NOT making my own container like i tried to last time but INSTEAD
a simple compose-based override of an existing ready-made one. I mount specifically .git and .devcontainer read only.
so this is the compose and this is the devcontainer.json
a simple compose-based override of an existing ready-made one. I mount specifically .git and .devcontainer read only.
so this is the compose and this is the devcontainer.json
![{
"name": "Ubuntu",
"dockerComposeFile": [
"docker-compose.yml"
],
"service": "app",
"workspaceFolder": "/workspaces/catra.top",
"remoteUser": "vscode",
"features": {
"ghcr.io/devcontainers/features/go:1": {},
"ghcr.io/devcontainers/features/hugo:1": {}
},
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:susc6mr26zl3wisqpqvdk33d/bafkreihvbvo3lvhw2wqmjsfielgo6k4tb2gacbxr3gup7fkyu5xonk3tu4)
October 8, 2026 at 10:36 PM
my solution so far is NOT making my own container like i tried to last time but INSTEAD
a simple compose-based override of an existing ready-made one. I mount specifically .git and .devcontainer read only.
so this is the compose and this is the devcontainer.json
a simple compose-based override of an existing ready-made one. I mount specifically .git and .devcontainer read only.
so this is the compose and this is the devcontainer.json
n like you can think of defense in depth and layers but like
DevContainers dont give you very many layers! any infostealer in a npm package whose LLM has the foresight to think of devcontainers can do so trivially. these kinds of places "should" have attacks targeting developers and their tooling!
DevContainers dont give you very many layers! any infostealer in a npm package whose LLM has the foresight to think of devcontainers can do so trivially. these kinds of places "should" have attacks targeting developers and their tooling!
October 8, 2026 at 4:28 AM
n like you can think of defense in depth and layers but like
DevContainers dont give you very many layers! any infostealer in a npm package whose LLM has the foresight to think of devcontainers can do so trivially. these kinds of places "should" have attacks targeting developers and their tooling!
DevContainers dont give you very many layers! any infostealer in a npm package whose LLM has the foresight to think of devcontainers can do so trivially. these kinds of places "should" have attacks targeting developers and their tooling!
for example, i'm now finally exploring devcontainers properly on their own merits in more depth.
first thing, devcontainer.json has initializeCommand, which runs a host command on creation
this configuration file is typically in your project, which is automatically bind mounted RW in containers.
first thing, devcontainer.json has initializeCommand, which runs a host command on creation
this configuration file is typically in your project, which is automatically bind mounted RW in containers.
October 8, 2026 at 4:06 AM
for example, i'm now finally exploring devcontainers properly on their own merits in more depth.
first thing, devcontainer.json has initializeCommand, which runs a host command on creation
this configuration file is typically in your project, which is automatically bind mounted RW in containers.
first thing, devcontainer.json has initializeCommand, which runs a host command on creation
this configuration file is typically in your project, which is automatically bind mounted RW in containers.
October 6, 2026 at 3:01 PM
Thanks for coming to my Tools and Action yesterday about #DevContainers at @devoxx.com and for the discussions afterwards, here are the resources :
📜 github.com/philippart-s...
📜 github.com/philippart-s...
📜 github.com/philippart-s...
🎨 docs.google.com/presentation...
📽️ youtu.be/eyJ5LO-Kyuw?...
📜 github.com/philippart-s...
📜 github.com/philippart-s...
📜 github.com/philippart-s...
🎨 docs.google.com/presentation...
📽️ youtu.be/eyJ5LO-Kyuw?...
GitHub - philippart-s/dev-containers-talk: Source code for Dev Containers talk
Source code for Dev Containers talk. Contribute to philippart-s/dev-containers-talk development by creating an account on GitHub.
github.com
October 7, 2026 at 8:08 AM
Thanks for coming to my Tools and Action yesterday about #DevContainers at @devoxx.com and for the discussions afterwards, here are the resources :
📜 github.com/philippart-s...
📜 github.com/philippart-s...
📜 github.com/philippart-s...
🎨 docs.google.com/presentation...
📽️ youtu.be/eyJ5LO-Kyuw?...
📜 github.com/philippart-s...
📜 github.com/philippart-s...
📜 github.com/philippart-s...
🎨 docs.google.com/presentation...
📽️ youtu.be/eyJ5LO-Kyuw?...
Practical: Zed if #latency and minimal UI matter most.
VS Code if you need remote, devcontainers, and a broad ecosystem.
Cursor only if you've already decided you want AI in the editor.
"Feels faster" isn't "does more" - that's TWO *different metrics* #coders people keep mixing up.
#devops
VS Code if you need remote, devcontainers, and a broad ecosystem.
Cursor only if you've already decided you want AI in the editor.
"Feels faster" isn't "does more" - that's TWO *different metrics* #coders people keep mixing up.
#devops
October 4, 2026 at 11:28 AM
DevContainersでwslcを使用するには、VSおよびDevContainer拡張を最新にした後、DockerコマンドのPATHにwslcを指定するだけ。
ちなみにdocker composeにはまだwslcは対応していないので注意。
以下で動作確認。
github.com/ishisaka/dev...
ちなみにdocker composeにはまだwslcは対応していないので注意。
以下で動作確認。
github.com/ishisaka/dev...
October 4, 2026 at 6:01 AM
DevContainersでwslcを使用するには、VSおよびDevContainer拡張を最新にした後、DockerコマンドのPATHにwslcを指定するだけ。
ちなみにdocker composeにはまだwslcは対応していないので注意。
以下で動作確認。
github.com/ishisaka/dev...
ちなみにdocker composeにはまだwslcは対応していないので注意。
以下で動作確認。
github.com/ishisaka/dev...
Allez, les cartables sont faits 💼 ... en route pour le #JUGSummerCamp 🏝️ !
Je vous propose de passer un moment avec moi demain à 17h15 pour parler #DevContainers 🐳.
On pourra aussi discuter #IA et #OVHcloud si vous êtes sages 😇.
A demain 👋
Je vous propose de passer un moment avec moi demain à 17h15 pour parler #DevContainers 🐳.
On pourra aussi discuter #IA et #OVHcloud si vous êtes sages 😇.
A demain 👋
September 3, 2026 at 1:32 PM
Allez, les cartables sont faits 💼 ... en route pour le #JUGSummerCamp 🏝️ !
Je vous propose de passer un moment avec moi demain à 17h15 pour parler #DevContainers 🐳.
On pourra aussi discuter #IA et #OVHcloud si vous êtes sages 😇.
A demain 👋
Je vous propose de passer un moment avec moi demain à 17h15 pour parler #DevContainers 🐳.
On pourra aussi discuter #IA et #OVHcloud si vous êtes sages 😇.
A demain 👋
New blog post. I recently changed roles at work from a mostly Frontend Focused Engineer to a more Developer Experience Focused Engineer. It's been a really interesting shift away from my normal. I decided to write about it. #engineer #devex #javascript #typescript #go
quincarter.com/posts/from-f...
quincarter.com/posts/from-f...
New Role, Same Mindset: what Frontend Taught Me About Developer Experience Work - Quin Carter - Brain Dump
I recently moved into a role leaning heavily on Docker, devcontainers, and overall Developer Experience work after spending most of my career in frontend engineering. The tools changed, but the job; ...
quincarter.com
September 1, 2026 at 1:29 AM
New blog post. I recently changed roles at work from a mostly Frontend Focused Engineer to a more Developer Experience Focused Engineer. It's been a really interesting shift away from my normal. I decided to write about it. #engineer #devex #javascript #typescript #go
quincarter.com/posts/from-f...
quincarter.com/posts/from-f...
デスクトップアプリから使えるCodexいいよ！みたいな話を聞くのだがDevContainers on WSL2の民はどのように使えば良いのかよく分かっていません！
August 30, 2026 at 11:22 AM
デスクトップアプリから使えるCodexいいよ！みたいな話を聞くのだがDevContainers on WSL2の民はどのように使えば良いのかよく分かっていません！
やっぱりClaude Code Routinesの環境設定、リポ選択式なんだからDevContainers読み込んでほしい…CodeSpacesと同じように
August 29, 2026 at 1:29 AM
やっぱりClaude Code Routinesの環境設定、リポ選択式なんだからDevContainers読み込んでほしい…CodeSpacesと同じように
What are you using for dotfile management these days? I use chezmoi, but am looking for something easier for applying them inside devcontainers and without having to fiddle with symlinks myself. #LazyEngineer
August 28, 2026 at 12:14 AM
What are you using for dotfile management these days? I use chezmoi, but am looking for something easier for applying them inside devcontainers and without having to fiddle with symlinks myself. #LazyEngineer
dev-containers-cli plus devcontainers/base:ubuntu26.04 makes a power couple
August 23, 2026 at 10:58 PM
dev-containers-cli plus devcontainers/base:ubuntu26.04 makes a power couple
I installed the developer edition of Bazzite to try VSCode with devcontainers. I was instantly bombarded with UI/UX information. The AI chat features being visible and suggested in every menu makes me feel gross even though I don't use them. So, uh, I'm gonna rebase to regular Bazzite. Ulgh.
August 22, 2026 at 5:07 PM
I installed the developer edition of Bazzite to try VSCode with devcontainers. I was instantly bombarded with UI/UX information. The AI chat features being visible and suggested in every menu makes me feel gross even though I don't use them. So, uh, I'm gonna rebase to regular Bazzite. Ulgh.