Live data from Hacker News

Switching to Claude Code and VSCode Inside Docker

timsh.org

11–20 of 170 posts

Re: Switching to Claude Code and VSCode Inside Docker

#11
Yes please, more containers-first thinking for all things AI. The fact that this has been largely absent from most discussions and demos regarding agents and vibe-coding seems like a big red flag to me. I mean if we're going to YOLO the code, perhaps we should at least pay some attention to the dev / test harness?

It's worth thinking about reproducibility even if you're not concerned about security. We would not have to argue so much about the effectiveness of something like vibe-coding if everyone could simply share process/tooling without tons of custom setup. And even if you're not worried about filesystem sandboxing and leaking secrets like ssh keys, even if versioning with git is enough of an undo button for you.. who wants to clutter their whole system with a ton of new language stacks and/or weird dependencies for every small experiment? Most experiments with the new hotness are going to fail, so we should expect to do a lot..

Re: Switching to Claude Code and VSCode Inside Docker

#12
Containers do seem to work really well for agents. It lets them run in parallel! Giving them sudo also lets them do interesting things you wouldn’t want them doing on your desktop, eg. installing tools or debugging with tcpdump. (I am working on agent-in-a-container: sketch.dev)

Re: Switching to Claude Code and VSCode Inside Docker

#13

[flagged]

Yeah, I don't think you deserve the down votes for expressing an opinion (except maybe that it doesn't add a lot to the conversation), but speaking from personal experience, the whole AI coding thing has been pretty amazing for me.

I'm technical, I can read code (even write some of it), but actually completing things or getting started on serious projects is really hard: partly because I am not a professional develop (and so everything is hard) and partly because of time constraints. AI agents address both of these concerns very well and I've been able to produce things I wouldn't have thought possible. Are they ready for Prod? Maybe not, but at least they WORK and that's soo much more than anything I've managed in the past.

Re: Switching to Claude Code and VSCode Inside Docker

#14
From what I can gather, this is part of the idea/appeal behind something like https://phoenix.new/. The AI Agents have total control over the environment and can use all of the associated system tools as a result, without putting your own machine at risk. Once things are kinda working, you can pull it out and work locally.

Re: Switching to Claude Code and VSCode Inside Docker

#15
post #9
post #4

I put in a full day trying to get Claude Code and VSCode to work inside Docker. I wasn't able to get the window to properly display in my wayland session.

I don't know if it's appropriate for your case, but devcontainer https://devcontainer.community/awesome >, code-server, or Eclipse Theia are basically VSCode over http and will mimick the GitHub.dev experience. I'm guessing a lot of your heartburn was trying to get the graphical parts of Electron to operate inside docker but it's really not good at that I did see the VSCode part, but it might interest you that the Je…

> but devcontainer https://devcontainer.community/awesome>,

404

Re: Switching to Claude Code and VSCode Inside Docker

#17
post #9

Earlier quoted context omitted.

I don't know if it's appropriate for your case, but devcontainer https://devcontainer.community/awesome >, code-server, or Eclipse Theia are basically VSCode over http and will mimick the GitHub.dev experience. I'm guessing a lot of your heartburn was trying to get the graphical parts of Electron to operate inside docker but it's really not good at that I did see the VSCode part, but it might interest you that the Je…

> but devcontainer https://devcontainer.community/awesome >, 404

Here's the intended link target: https://github.com/devcontainer-community/awesome-devcontain...

Re: Switching to Claude Code and VSCode Inside Docker

#18
post #16

This kind of behaviour is hilarious, either use the tools with their caveats, or actually make a stand by not using them. 60's movements would not be possible in current times.

"accept things how they are, or give up"

would not be possible, indeed

Re: Switching to Claude Code and VSCode Inside Docker

#19
post #16

This kind of behaviour is hilarious, either use the tools with their caveats, or actually make a stand by not using them. 60's movements would not be possible in current times.

"accept things how they are, or give up" would not be possible, indeed

Standing up is not giving up, thanks for confirming my remark.

Re: Switching to Claude Code and VSCode Inside Docker

#20

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool…

Thanks
Post reply on HN