MicroVMs: Run isolated sandboxes with full lifecycle control
1–10 of 222 posts
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#2does it have gpu support?
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#3This seems roughly similar to Google's Cloud Run gen2 instance types. My understanding is with the second generation, they are running microvms which are bootstrapped from a container image.
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#4does it have gpu support?
Not that I can find in the docs anywhere. Compute only.
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#5How does this compare to E2B?
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#6does it have gpu support?
No, it doesn’t seem like it.
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#7does it have gpu support?
It is supposed to be a sandbox that you can invoke from agent, langchains of the world, coding agents etc.
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#8> MicroVMs support up to 8 hours of total runtime
Does this mean you effectively can't use them as long-lived developer environments? It sounds like even if you suspend them, this is the hard limit on the total time it can run.
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#9How does this compare to E2B?
e2b supports UDP and the pricing structure is different.
Re: MicroVMs: Run isolated sandboxes with full lifecycle control
#10How's this different from Firecracker?