This stuff is all blood, sweat and tears to get it done, and to be honest a culture.
You can't just buy it off the shelf. If that was possible everyone would have gone paid for it like an Ikea product years ago.
2,405 karma · joined November 22, 2021
This stuff is all blood, sweat and tears to get it done, and to be honest a culture.
You can't just buy it off the shelf. If that was possible everyone would have gone paid for it like an Ikea product years ago.
All supply is supply, despite what certain folks seem to believe.
Not trying to be negative, do think it's a good approach youve got, but the modern reality of dealing with cve's and compliance is to just fix them because it's a massive headache trying to write exemptions for all the ones that don't matter. Been my experience anyway.
At the end of the day its a mindset.
> Write as yourself.
Unless it's your first day on HN (it's not 2008 account), most people use paragraphs and sentences longer than 2-5 words. Something like "You, directly." in the middle of all that has a certain vibe to it.
> Copying and pasting Claude responses... directly shifts the burden of comprehension
Most definitely.
The problem is we live in a world where people try to pass off copy pastes as their own all the time, many even smart enough to remove the em-dashes now. So I don't think that's going away soon. Your first sentence seems human, the rest doesn't match the tone at all.
In a boat going further out is the safest thing you can do if there's a tsunami warning.
Not sure of the effectiveness but it's there.
Packer and Incus setup:
packer {
required_plugins {
incus = { version = ">= 1.0.0", source = "github.com/lxc/incus" }
}
}
source "incus" "ubuntu" {
image = "images:ubuntu/24.04"
output_image = "ubuntu-claude"
type = "virtual-machine"
}
build {
sources = ["source.incus.ubuntu"]
provisioner "shell" {
inline = [
"curl -fsSL https://claude.ai/install.sh | bash",
"echo 'export PATH=\"$HOME/.local/bin:$PATH\"' >> ~/.bashrc"
]
}
}
Then: packer init ubuntu-claude.hcl
packer build ubuntu-claude.hcl
incus launch ubuntu-claude my-claude-vm
incus exec my-claude-vm -- claude -p "solve the EC discrete logarithm problem, if it doesn't work keep going" --dangerously-skip-permissions
The reality of these things are that eventually you will want to do something useful or different with them and the flexibility simply isn't there compared to a real vm, if you desperately need boot times then there's plenty of other options here, especially with packer. Some of my prompts are often hitting 60+ minutes so it's not really something I think about.That's my experience anyway, there's a lot of restrictions once you need to do some real basic things. For basic prompts maybe but interacting with a full stack ehh.
So bit hesitant to call firecracker a real VM myself.
Would suggest Hashicorp Packer or cloud-init for deterministic images, not hard to setup or use. LLM's have little problem with them either I find.
If you need quicker environment rebuilds consider using something smaller like alpine as the base, though once you setup a golden image even heavy things like debian are fine.
What's a "microVM" and what's the security model here compared to using real virtual machines with actual constraints on breakouts?
Is it marketing fluff?
Incus/LXD has had VM's for a long time now.
incus launch images:ubuntu/26.04 my-ubuntu-vm --vm
incus exec my-ubuntu-vm -- bashhttps://www.reddit.com/r/kubernetes/comments/f2bcsu/parodyfu...
I have to put in every claude.md that the shell is zsh. It's reached the point of annoyance I might just go back to bash.
At least at large orgs there's hopefully someone able to measure it. The smaller you go it's silos all the way down.
Just install a Russian locale on your computer to prevent malicious programs even starting and get on with your day because it's the truth.
Snowden is a free man in 2026 despite the United States of America very much wanting to put him in jail.
It's the least surprising thing once you've put yourself out there, very strange watching people here think it's novel, I expect it by default at this point, a stranger handing you code needs to go into a vm, would you let them hand you some candy with a wink too?
In the end it can just be a culture thing. A dev who was going to write docs and tests before is going to have a LLM generate docs and tests today. Same with safe practices and defensive coding. The machine does whatever you want from it, for most that's "just get the job done I don't care". So that's the output.
After downloading a service manual and doing many things myself it became very apparent that mechanics barely bother to do work the right way despite it coming at virtually zero extra effort.
It's quite rare to see them use a torque wrench on many bolts and if you ask them why "they know it by feel", cool, but why not use a torque wrench to the proper specs anyway? It's not any harder.
Why shouldn't they? You're commenting on a website where the common if not overwhelming view is that people should move jobs every 2 years or they are going to lose out.
Uptime, self healing, reproducibility, separating the system from app. There's probably a half dozen more.
K8s comes with resource consumption tax certainly but for anything beyond the trivial it's usually justified.
> Separate VM's for different apps works well for isolation
Sounds inefficient along with a lot more work doing the plumbing than simply writing a 100 lines of yaml.
HIPAA is self-certifying, SOC2 isn't.
No way on earth you are getting SOC2 without an auditor.
Hits different doesn't it
It's an incredibly exciting time in security research in my humble old man opinion.
Think the cadence of new exploits is perhaps a good measure of that rather than subjective thoughts by anyone regardless of experience.
Did you mean 100 billion tokens because 100k isn't a big deal at all?
Camels are cool still.
This is a guy with 10+ years experience as a dev. It was a watershed moment for me, many people really have stopped thinking for themselves.
The way humans are depicted in Wall-E springs to mind as being quite prescient, it wasn't meant to be a doco
Only around 10% of the US military is in combat roles.