Earlier quoted context omitted.
You can take a snapshot of a microVM and roll back. I've never heard of this being done with containers.
You can have a volume mount into your container backed by whatever block storage which may have snapshotting or format with a FS that supports snapshots.
How we run Firecracker VMs inside EC2 and start browsers in less than 1s
171–180 of 251 posts
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#172Earlier quoted context omitted.
I haven't personally tried, so I can't say for certain, but Lambda has publicly stated they run on bare metal EC2 instances, presumably the supply of whatever instance types they use should be fairly healthy
You're talking about AWS Lambda? - Their use of bare metal isn't necessarily the latest gen hardware - AWS Lambda is part of AWS, and obviously has privileged access to supply
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#173Earlier quoted context omitted.
> But if I did so for scalping purposes? Then yeah, I'd agree it's unethical. Is scalping actually unethical though? Sure it's unpopular, but I'd argue that's just your average person not properly grasping supply and demand and thinking through the consequences. If you want to sell something below market then you should raffle it off and take extensive measures to prevent transfer of ownership. The current practice i…
Noone thinks concert ticket sales are an open market tho. They have one seller that sets the price, no competition between different sellers. It only becomes a "market" after scalpers buy all contingent to resell.
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#174Earlier quoted context omitted.
Noone thinks concert ticket sales are an open market tho. They have one seller that sets the price, no competition between different sellers. It only becomes a "market" after scalpers buy all contingent to resell.
Unbelievable how somebody could defend scalping. There is no ethical or moral value in that practice outside of "I can earn money with that".
Similarly I do not attempt to blame the rank and file employees of the ad tech industry for the actions of their employers, nor of the defense industry for the actions of the government. As an individual living under such a system either you move to make money when the opportunity arises or someone else will instead and you will lose out.
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#175Earlier quoted context omitted.
I'd counter that your attitude is a techno-authoritarian one. Why should anyone have any say over how I access and use a publicly available resource? At least so long as my actions don't directly cause technical problems for the service operator.
Look, it wasn't _my_ request that made the server fall over, it must have been one of the other several thousand thoughtless scrapers running on the website that caused it to die.
As far as anti-bot countermeasures go I quite like proof of work solutions since those disproportionately impact high volume scrapers without noticeably impeding a small hobby project.
Unfortunately the operators of many major websites appear to want something akin to DRM with the excuse of bots used merely as window dressing.
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#176Something elided here is that nested virtualization on regular EC2 instances has only been possible since February this year[1] - before this, you had to use a metal EC2 instance to run Firecracker VMs. 1. https://aws.amazon.com/about-aws/whats-new/2026/02/amazon-ec...
And metal instances are MEGA slow to start and stop.
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#177Earlier quoted context omitted.
I'd counter that your attitude is a techno-authoritarian one. Why should anyone have any say over how I access and use a publicly available resource? At least so long as my actions don't directly cause technical problems for the service operator.
Look, it wasn't _my_ request that made the server fall over, it must have been one of the other several thousand thoughtless scrapers running on the website that caused it to die.
And if everyone did this, it'd be a real problem. The stores would be clogged up by geeks writing notes in little books with Parker Jotters and just basically wasting space and taking up air conditioning while they sleuth out the best way to put the screws to the company for a few measly dollars.
That'd be awful.
But not many people ever did that in stores, and not many individual people are doing that today with the web. It's really not a problem.
(And if a website in 2026 can't stand the burn of several thousand personal scrapers that are operated by people who actually want to buy stuff from it, then maybe that system simply sucks and needs to be rethought.)
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#178The challenge they encountered was at a different layer: horizontally scaling the underlying EC2 infrastructure. At the time, native EC2 fleet autoscaling wasn't yet supported by the platform, so they chose to take ownership of that part of the stack and build directly on Firecracker.
It's also worth noting that Unikraft is actively working on transparent infrastructure autoscaling (with live migration), so the gap they encountered is being addressed. The article's title may give the impression that unikernels were the bottleneck (they weren’t, and our platform transparently support Linux VMs as well), when in reality the decision was driven by infrastructure orchestration requirements rather than browser runtime capabilities.
As an aside, we love Browser-Use <3 and we still work together closely!
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#179We run a screenshot API (ApiFlash) with Chromium packaged in an AWS Lambda container image instead of Firecracker on EC2. AWS Lambda gives you the isolation and autoscaling for free which is ideal for spiky stateless work like screenshots. I believe we get mostly the same benefits compared to browser-use solution but with a much much simpler architecture. The tradeoff is the AWS lambda cold starts, but in practice se…
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#180What is firecracker needed? Couldn’t this just run in a container directly? I understand some of the isolation concerns but a browser and container breakout is a billion dollar CVE, no?
Most mature and/or security conscious providers don't consider containers to be a secure isolation boundary (with Microsoft being a notable exception, though it's unclear whether that's a failure of internal policy or incompetent enforcement of policy). Containers provide a much broader attack surface than VM's, and since they're not considered secure as an industry standard there's likely to be less resources put to…