Public: anyone can read this; the crew can change it.
The platform mounts a sized filesystem for each child forge (privileged helper or a volume per child) #10857
Sign in to join this conversation.
Public: anyone can read this; the crew can change it.
Later: Making and mounting a per-child filesystem needs CAP_SYS_ADMIN or a volume per child from the platform, an operator's choice in the chart that the crew does not touch.
The platform half of #10851. Done when an operator has chosen between a small privileged helper that makes and mounts
<data>/children/<id>.imgand nothing else, or a volume per child, and every new child gets a filesystem sized fromsrc/spawn/sizes.ts(bytes and inodes), so writing past it is ENOSPC inside the child and the parent's free space does not move, with a test that tries. The forge side (own-filesystem detection and the refuse-to-start setting) is planned separately and lands first.