Support --cgroup-parent, bridge name option, enable_icc=false and user namespace remap for hosting multi-tenant apps Context

Aperta
#213 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, linux, rust

Direzione di ricerca

Start by locating how Kiri reads Docker API HostConfig and network options, and how it configures cgroups, Linux bridges, and user namespaces. Check which of the four controls are currently unsupported and whether ignored options can be rejected with a warning or 400 response. Done means the supported behavior and isolation boundary are clearly defined, with tests or documentation covering each requested control.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
What you're trying to do

I am evaluating Kiri as a runtime for a shared-hosting panel that runs untrusted user binaries, one project per network, in containers from gcr.io/distroless/static with --read-only, --cap-drop=ALL, --security-opt no-new-privileges, and --user uid:uid. Kiri already handles memory (--memory), CPU (--cpus), --pids-limit, read-only rootfs, capabilities, and no-new-privileges, and it forces memory.swap.max=0, which is what we want. Thanks for that.
The following flags are accepted by the Docker API but silently ignored. The container starts, so nothing reports an error, but the protection is missing:
1. HostConfig.CgroupParent is not read. Containers do not go into the given slice, so we cannot set one aggregate CPU/memory limit per project across its containers.
2. com.docker.network.bridge.name network option is not read. Bridges are always named kiriN. This breaks host firewall rules that match bridge names (iifname "gsh-p-*").
3. com.docker.network.bridge.enable_icc=false is not implemented. Containers on the same user-defined network can likely still reach each other. Please confirm and tell us how to get this isolation.
4. User namespace remap (userns-remap or per-container UsernsMode) is not available. Root inside the container is root on the host kernel, with no uid mapping. We would like at least an option to map container root to an unprivileged host uid, or a documented statement on the isolation boundary.

What you'd like Kiri to do

Why it matters
These are defence-in-depth controls for running code from different tenants on one host. Without 1 and 4, a single project cannot be capped as a group, and a container compromise has less separation. Without 2 and 3, a firewall rule written against the bridge name silently does nothing.
Requested
• Either implement the four items above, or state clearly which are out of scope, so users know what the isolation boundary is.
• For any flag that is ignored, return a warning or a 400 instead of silently accepting it.
Environment: Kiri Linux (host, no VM), commit 1befa94 / release , Debian 13 amd64.

Would you like to build it?

No, just suggesting it

Lingua principale
Rust
Stelle
7.5k
Fork
329
Merge medio
7h 48m
PR unite (30g)
105

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di libracoder/kiri

Tutte le issue di libracoder/kiri

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.