Live data from Hacker News

Switching to Claude Code and VSCode Inside Docker

timsh.org

161–170 of 170 posts

Re: Switching to Claude Code and VSCode Inside Docker

#161
post #27

Earlier quoted context omitted.

Except you glossed over the part where the person said they lacked time. There is programming the art and programming to solve a problem. The art is great - I’ve written software for decades. Life dictates I no longer have as much time, but I still want to solve problems. AI helps me do that in the limited that I have.

The fatal flaw in your theory is that Docker, Claude, and whoever else will add an infinite amount of time spent debugging once you have a sufficiently complex problem, which is usually within 1-7 days of using it. Please explain to me how I'm wrong. in the event you don't want to hear how I'm right, I am forstalling that while waiting for your reply

This thread is full of examples of people using the tools successfully. I'm also not sure where you're getting the 1-7 days from.

And someone who has the time may learn more by doing things without AI, but that's not what's being discussed. The person you originally responded to and I said we don't have the time.

It's a bit like arguing that AI audiobooks shouldn't exist because they are worse than human read. That may or may not be true, but that's not the discussion. AI may be the only reason an audiobook exist at all for certain books. AI coding is often the same way where someone can build a lot more than they could prior, even if it's imperfect, it may still solve their problem.

Re: Switching to Claude Code and VSCode Inside Docker

#162
post #118

Earlier quoted context omitted.

I use VMs myself. I use Proxmox and have it setup so that I can spin up a fresh VM in around 10-20 seconds when needed. I also like that I can take snapshots. I really want to limit the amount of software I am installing on my main system due to possible security issues.

Do you have any example scripts for your setup? I have recently moved to a VM only development workflow, but still feeling some growing pains as I figure out a good setup. I run my IDE in the guest, which is kind of crummy - responsiveness is worse + the VMs are a lot heavier than a headless code setup would be. I have thought about using a Flatpak IDE with filesystem access disabled as a potential middle ground solu…

I have taken cloud images and set them up with 'cloud-init'. So I can bring them up very quickly.

Re: Switching to Claude Code and VSCode Inside Docker

#163
post #38

Earlier quoted context omitted.

Have you tried setting up multiple git worktrees as well? I wonder if that doesn’t solve most of the issues.

I have, but I just found that a bit tedious to manage manually. Maybe another version of this script would just be to automatically create a worktree, run a prompt in that, and then have the script manage the results, and clean up the worktree at the end.

One thing that I’ve found works well is to permanently have a few numbered branches checked out as worktrees, keep them up to date with main, and then when you want to do a task in parallel you just pick an existing branch rather than creating and deleting worktrees every time.

This lets you persist local databases, IDE project settings and so on for each worktree too.

Re: Switching to Claude Code and VSCode Inside Docker

#164

Earlier quoted context omitted.

> I'm using claude --dangerously-skip-permissions all day and haven't had a single issue. Yet. You haven't had a single issue yet.

Correct. The number of times I’ve had Claude ask permission to rm -rf paths with .. elements is more than zero.

I have in fact had Claude (running on Cursor) do the equivalent of rm -rf /. It happens.

Re: Switching to Claude Code and VSCode Inside Docker

#165

Earlier quoted context omitted.

Even locally, Claude in multiple terminal tabs/windows can do different tasks in parallel

They can, but I find it harder to review if you are trying to get Claude Code to do anything non-trivial. I've seen some people make multiple git worktrees so they can have two instances of Claude Code working independently, but I found that to be tedious to manage.

Isn't there tooling for helping to manage this

Re: Switching to Claude Code and VSCode Inside Docker

#166
post #65

Earlier quoted context omitted.

Just tried it... and it says it's client-only, but when I try to run the SSH provider using my Rapberry Pi it says it needs `docker` to be installed on it :/. So it's not just client-only, is it?

Isn't that what client-only means?

No, client-only means Devpod is contrasting itself to Coder, which requires a central server to orchestrate the containers it creates. Devpod does not. It does still have dependencies, though, among them Docker.

Re: Switching to Claude Code and VSCode Inside Docker

#167
post #151

Earlier quoted context omitted.

It's their reimplementation.

That’s not what that word means

They do indeed use a different implementation of these features than the one that ships with VSCode, though they're not the original authors of it. They used to host their version separately here: https://github.com/anysphere/open-remote-ssh

But I guess they've just rolled it into the Cursor repo? Idk, because Cursor itself is proprietary.

There's a similar extension for WSL integration, though I'm not 100% sure if Cursor's implementation of this feature is based on it: https://github.com/jeanp413/open-remote-wsl

You can sideload proprietary VSCode extensions to add them to VSCodium or some downstream fork, but you may also have to patch the extensions themselves because some of them refuse to run if they aren't being used with Microsoft's VSCode: https://github.com/OliverKeefe/vscode-extensions-in-vscodium

Re: Switching to Claude Code and VSCode Inside Docker

#168
post #158

Earlier quoted context omitted.

Like, oh you need to install this extremely heavy tool on your server... but yeah it's still client-only, trust me?

No, client-only as in this is the client only. You need a corresponding server. Are you thinking of "runs locally"?

Mate, if you need to install something on a server how the hell can it be called client-only??? eMacs is an example of client-only perhaps, with TRAMP as it works purely on top of SSH , though you could argue it still isn’t client-only as it requires the SSH server to be enabled… so I thought the SSH connector for this would also work the same way but it also requires a full freaking Docker install not just SSH. This is totally misleading.

Re: Switching to Claude Code and VSCode Inside Docker

#169
post #65

Earlier quoted context omitted.

devpod is quite nice for this https://devpod.sh/

Just tried it... and it says it's client-only, but when I try to run the SSH provider using my Rapberry Pi it says it needs `docker` to be installed on it :/. So it's not just client-only, is it?

It's client-only because if you install it on a machine with Docker, you don't need a server to use devcontainers.

Docker is required to use devcontainers, so there's really no getting around the Docker requirement

Post reply on HN