gbxk

Joined 1 year ago

Karma
71
Submissions
38
Member since
Sep 11
Gary Bécigneul Webpage: beci.me Contact: g{@}beci{dot}me
View on Hacker News

Recent submissions

Comment · 2 months ago
Comment · 2 months ago
Comment · 2 months ago
Comment · 2 months ago
That does not look planned.
Comment · 2 months ago
Nobody said that’s the only safeguard. When the attack surface is all of language you better have a defense-in-depth philosophy or as close as you can to that.
Comment · 1 year ago
Update: Katakate now supports ARM architecture (on Linux) thanks to a PR merged from Katakate's first external GitHub contributor: @spullara. Thank you!
Comment · 1 year ago
Test passed, PR merged
Comment · 1 year ago
As promised: https://github.com/Katakate/k7/tree/fix/no-dns-res-in-lockdo...

Will merge that in after it passes all network tests on a clean/wiped instance.

Comment · 1 year ago
Thanks! I'll review Arrakis and come back. E2B is often considered harder to setup and less AI engineers friendly for direct stack contributions, as Katakate is the only alternative fully implemented in Python (core modules, Typer CLI, FastAPI, Python SDK).

Our native K8s support and exposition of K8s API also makes it friendly to devops.

Finally, our deploy/infra stack is lean and tightly fits in a single Ansible playbook, which makes it easy to understand and contribute to, letting you rapidly gain full understanding and ownership of the stack.

Comment · 1 year ago
Thanks! Yes: Katakate provides much stronger isolation, since it uses hardware virtualization (via Kata Containers and Firecracker) while gVisor relies purely on software sandboxing in user space.

gVisor isolates containers by intercepting system calls in a user-space kernel, so it can still be vulnerable to sandbox escape via gVisor bugs, though not directly through Linux kernel exploits (since gVisor doesn’t expose the host kernel to the container).

Katakate also provides more than isolation: it offers orchestration through Kubernetes (K3s)

You could create a gVisor RuntimeClass in Kubernetes to orchestrate gVisor sandboxes, but that would require extra setup.

Comment · 1 year ago
Thanks for sharing, adding it to my list.
Comment · 1 year ago
Very cool! Apple containers run on Apple ARM so it's complimentary to my stack which doesn't support ARM yet (but soon will when extending to Qemu which supports ARM). Thanks for sharing!
Comment · 1 year ago
This is an excellent point. I moved this to #1 on the TODO list. I'll deny all DNS resolution by default until Cilium is integrated, if that passes the basic functionality tests.

I'll also add to the roadmap whilelist/deny for container pulling.

Thanks!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton