Earlier quoted context omitted.
I like the CLI for commands, but would rather work with an agent chat interface for vibing, which unfortunately I’m becoming increasingly reliant on, even though it’s gotten me into trouble with larger projects. I have many environments locally, some dependent on others, and some require local databases. I use containers in production, but not always locally. It’s almost a hellscape situation for trying to setup a fu…
> which unfortunately I’m becoming increasingly reliant on, even though it’s gotten me into trouble with larger projects You could… not do this. You know it causes you problems, you consider it unfortunate that you’re becoming more reliant on it, and yet for some reason you’re choosing to continue anyway. Why are you doing that?
Switching to Claude Code and VSCode Inside Docker
81–90 of 170 posts
Re: Switching to Claude Code and VSCode Inside Docker
#82has anyone faced this?
Re: Switching to Claude Code and VSCode Inside Docker
#83i don’t get the worry. i run these models all day without any sandbox and even leave them running while i walk away. i haven’t had a rm -rf kind of situation ever or even a hint of model going towards it. even gemini 2.5 at it’s lowest doesn’t do that. has anyone faced this?
Re: Switching to Claude Code and VSCode Inside Docker
#84Re: Switching to Claude Code and VSCode Inside Docker
#85Honest question: why do people prefer developing code inside a docker? I get the benefits of docker as a deployment unit, but wouldn’t configuring a dev container and using it a hassle nonetheless, compared to not doing them at all?
Re: Switching to Claude Code and VSCode Inside Docker
#86Earlier quoted context omitted.
> If you are a VSCode hater (like me) What are some reasons to hate VSCode?
It’s clumsy as hell. It’s neither a good editor, which focus on being fast when doing things with text, nor a good IDE, which is more about the tooling and getting a project done. It’s trying to be both at the same time. And the result is bad at both.
Re: Switching to Claude Code and VSCode Inside Docker
#87Honest question: why do people prefer developing code inside a docker? I get the benefits of docker as a deployment unit, but wouldn’t configuring a dev container and using it a hassle nonetheless, compared to not doing them at all?
Re: Switching to Claude Code and VSCode Inside Docker
#88Earlier quoted context omitted.
Any interest in sharing the script?
I'm afraid it is not that shareable as it contains a lot of dependency management and setup that is specific to my setup and projects. But it's not too complicated. You could probably re-create your own version fairly quickly. It's just a Dockerfile that installs dependencies, an entrypoint that invokes claude, and some wrapper scripts that handle creating the container, passing through the prompt, and managing the r…
Re: Switching to Claude Code and VSCode Inside Docker
#89Re: Switching to Claude Code and VSCode Inside Docker
#90i don’t get the worry. i run these models all day without any sandbox and even leave them running while i walk away. i haven’t had a rm -rf kind of situation ever or even a hint of model going towards it. even gemini 2.5 at it’s lowest doesn’t do that. has anyone faced this?
However, if you are familiar with Pliny the Liberator's work, essentially all modern models are easily jailbroken, such that the original prompt can be overridden. All it will take for your agent is to download a malicious payload, perhaps disguised as a relevant library or documentation for the task at hand, and it can be running whatever the attacker tells it.
An 'rm -rf /' would be a pretty mild outcome. The more likely one would be the attacker silently installs malware on your machine.