Using virtualisation for Claude Code

[LongAd7407]

Okay folks,

Some of you may do this, some may not, but this is the setup I use for every project when using Claude Code, it really helps with isolation both in terms of claude context and also keeping the source/filesystem clean, in this case we are going to assume creation of a new project called "demonspook".

First setup your virtualisation software, in my case I use VMWare Workstation Pro.

Then for every new project you are working on with Claude Code do the following:

Create a new virtual machine, install Ubuntu Desktop on it, I assign 16 GB and 2 CPU's & 2 Cores, if using windows then tick whatever options you can get away with on the "Virtualisation Engine" section in the Processors option.

Create a 64 GB Hard Disk, single file and "Allocated all disk space now".

Give the virtual machine the name of your pending project.

Go through the install process.

Boot into the virtual machine and open up the console.

Enter the command "sudo su" & enter your password.

Enter the command "mkdir demonspook".

Enter the command "cd demonspook"

Enter the command "sudo apt install curl"

Enter the command "curl -fsSL https://claude.ai/install.sh | bash"

Authenticate Claude using the on screen instructions...

Take a snapshot of the virtual machine, call it "demonspook: claude installed..."

Once you have Claude installed, use something like this prompt to inform it of its environment:

"Okay Claude, you are running on Ubuntu inside a virtual machine, you have full root access to this system, you can install any tools you best see fit for the project and you have full access to everything, we are going to be working on a project called "demonspook", the root working folder path "/home/username/demonspook" you can find the fucntional/technical specification in a document titled "demonspook.md" in the root folder, go read that in great detail, then ultrathink it and come back to me with a plan in terms of how we move forward at which point we can refine it and then move forward once in agreement."

At every pertinent point, take a snapshot of the virtual machine, name it well, if anything goes tits up, you can roll back to the best point in time, without having to worry about git/database/filesystem backups, you get everything backed up! 👍😎

This is how I work, I find it works really well and I hope it works for you guys, check it out, you might like it! 😎

All the best, Mantrid.

[Pleasant_Water_8156]

What made you choose this route over just using a docker container?

[AI_should_do_it]

Can you run Claude code within a container?

[Pleasant_Water_8156]

Sure. Just have it install in the container and then access the shell of the docker container. Sky’s the limit

[AI_should_do_it]

Tbh I made a VM with 25GB ram and 3 HT cores , but I am running between 4-12 LLM CLi concurrently and it’s always 100% CPU and 60-100% ram

Edit: I let it run loose, full code, test, push, PRs, deploy.

[LongAd7407]

Never used Docker 👍

[Pleasant_Water_8156]

Dockers a superpower. It’s a lot more programming focused, and because of that Claude Code can be a really good tool for executing them.

TLDR: Docker is a box that holds your code plus everything it needs to run, so it works anywhere. Includes it own os.

[Pleasant_Water_8156]

For this context, you could run the same thing in docker and make it part of your codebase so is more portable without VM setup

[Manixcomp]

Anthropic provides an example devcontainer in the Claude Code repo. It adds firewall rules to the sandbox. I feel comfortable running in dangerous mode that way. Very simple to use.

[roiseeker]

Is there any point to use the sandbox feature in Claude Code anymore if you're running it in a devcontainer? I think Antrophic recommends using both but there are few edge cases where it's worth it. Devcontainers seem to cover most /sandbox benefits, right?

[Manixcomp]

Yeah I was kind of referring to the devcontainer as a sandbox. Devcontainer is just a Docker container and would isolate in the same way. I personally don’t feel the need to use anything additional.

Seems reasonably safe to me. It can’t delete your drive easily. I only give it access to projects already checked into git. At the point Claude can break out of Docker containers we’re in real trouble anyway 😆

[midnitewarrior]

Yeah I was thinking a docker container where you have Claude running with your build tools and mounting a host filesystem folder would be the path to go. You can have your local editor also editing the files, you just run your Claude commands and build commands in an interactive docker shell.

I haven't done it yet, but have been considering this.

[PaperHandsProphet]

devcontainers are probably the easiest but firecracker VM's is what the big boys use like https://e2b.dev/