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..
Switching to Claude Code and VSCode Inside Docker
11–20 of 170 posts
Re: Switching to Claude Code and VSCode Inside Docker
#12Re: Switching to Claude Code and VSCode Inside Docker
#13[flagged]
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
#14Re: Switching to Claude Code and VSCode Inside Docker
#15I 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…
404
Re: Switching to Claude Code and VSCode Inside Docker
#1660's movements would not be possible in current times.
Re: Switching to Claude Code and VSCode Inside Docker
#17Earlier 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
Re: Switching to Claude Code and VSCode Inside Docker
#18This 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.
would not be possible, indeed
Re: Switching to Claude Code and VSCode Inside Docker
#19This 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
#20If 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…