It's 2026 and `docker volume ls` still doesn't show size, usage, location, created, updated...
1
0
3
71
Many thanks to @_heyglassy and @PlanetScale for the ticket 🫶
0
0
2
61
Alexander Jung retweeted
Incredibly cool.
Unikraft is by far one of my favourite up and coming infra companies. Amazing engineering paired with a vision that addresses a lot of ops and cybersecurity questions the AI age has raised (it runs everywhere including local env, minimal auditable kernel)
Unikraft is by far one of my favourite up and coming infra companies. Amazing engineering paired with a vision that addresses a lot of ops and cybersecurity questions the AI age has raised (it runs everywhere including local env, minimal auditable kernel)
We rebuilt this with the team at @UnikraftSDK, and they wrote up the project from their side.
unikraft.com/blog/netlify-e…
0
1
6
230
Cool usecase!
It runs on @UnikraftCloud, on very small machines that do one job. OpenFGA uses about 18 MiB of memory, the API under 30. When nobody calls it, it sleeps.
There are 109 tests on the rules. Code is here, a star is welcome: github.com/guillempuche/d…
0
0
1
195
build a unikernel instead ✨
🗞️ unikernels were hard. key word: were.
ghuntley.com/unikernels
Justin Cormack, who worked on MirageOS back in the day, called me at the pub to talk about why unikernels are coming back. The friction that made them hard is gone; the operating system is design debt, and if you u should seriously consider them.
0
0
10
550
the european mind cannot comprehend: it's not possible for some folks to buy an AC right now in SF because there's a shortage of parts because they're being sold to data centres
0
0
0
78
it's demo time next tuesday with us at @UnikraftCloud and @omnaraai @kinglycrow @ishaansehgal @artahian @kushbhuwalka come by, see what we're up to and say hi👇
luma.com/k8f22yr1?tk=IX…
luma.com/k8f22yr1?tk=IX…
3
2
16
1,974
reminder: only 2% of the US market buys an AI product
there’s still so much to build and capture
there’s still so much to build and capture
1
0
6
355
been saying the same thing for the last 10 years but I’ll say it again:
Containers don’t contain. Isolates don’t isolate.
Run your workload in a VM. Let the hardware do the real work of physical guest separation.
Then, lock it down further, a stripped kernel with no user or shell. Then restrict networking from privileged host.
Containers don’t contain. Isolates don’t isolate.
Run your workload in a VM. Let the hardware do the real work of physical guest separation.
Then, lock it down further, a stripped kernel with no user or shell. Then restrict networking from privileged host.
"Several vulnerabilities" in the Linux kernel lwn.net/Articles/10974…
0
1
11
955
at @modal runtime and they ran "a million sandboxes" but it was just a gif; and no indication of how big and how much infra was needed to run it
you can do that on a single machine with @unikraftcloud
you can do that on a single machine with @unikraftcloud
0
0
7
404
