hakurei/fst, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/fst?h=develop2025-06-24T19:57:41Ztreewide: rename to hakurei2025-06-24T19:57:41ZOphestracat@gensokyo.uk2025-06-24T18:59:52Zurn:sha1:87e008d56de974947ebb99c2cc40b25d3c2cf43e
Fortify makes little sense for a container tool.
Signed-off-by: Ophestra <cat@gensokyo.uk>
fst: improve config2025-04-12T18:30:19ZOphestracat@gensokyo.uk2025-04-12T18:23:28Zurn:sha1:31b7ddd122d54c36edb101d2c8bdf230651f27d4
The config struct more or less "grew" to what it is today. This change moves things around to make more sense and fixes nonsensical comments describing obsolete behaviour.
Signed-off-by: Ophestra <cat@gensokyo.uk>
fst: check template2025-04-12T09:00:25ZOphestracat@gensokyo.uk2025-04-12T09:00:25Zurn:sha1:c460892cbdfa66a2cf1f0ebcec59cf550e67962e
Signed-off-by: Ophestra <cat@gensokyo.uk>
app/instance: wrap internal implementation2025-04-12T04:56:41ZOphestracat@gensokyo.uk2025-04-12T04:56:41Zurn:sha1:6309469e933a31a300fbf16d8e77f48dcee402d3
This reduces the scope of the fst package, which was growing questionably large.
Signed-off-by: Ophestra <cat@gensokyo.uk>
fst: mount passthrough /dev writable2025-04-11T11:01:54ZOphestracat@gensokyo.uk2025-04-11T11:01:54Zurn:sha1:ae6f5ede1928c9d0a2d480b6a924914e8599529f
Signed-off-by: Ophestra <cat@gensokyo.uk>
fst: rename device field2025-04-11T10:32:15ZOphestracat@gensokyo.uk2025-04-11T10:22:00Zurn:sha1:2f4f21fb183a1880c0363ad65f443b4af64a5359
Dev is very ambiguous. Rename it here alongside upcoming config changes.
Signed-off-by: Ophestra <cat@gensokyo.uk>
sandbox: relative autoetc links2025-04-11T09:54:00ZOphestracat@gensokyo.uk2025-04-11T09:54:00Zurn:sha1:996790946092a9291eb21e297d1f0f04deab8b42
This allows nested containers to use autoetc, and increases compatibility with other implementations.
Signed-off-by: Ophestra <cat@gensokyo.uk>
sandbox: implement autoetc as setup op2025-04-10T09:54:25ZOphestracat@gensokyo.uk2025-04-10T09:54:25Zurn:sha1:c806f43881223a85ad888f434e078dcc68de028d
This significantly reduces setup op count and the readdir call now happens in the context of the init process.
Signed-off-by: Ophestra <cat@gensokyo.uk>
sandbox/seccomp: rename flag type and constants2025-04-07T16:59:45ZOphestracat@gensokyo.uk2025-04-07T16:59:45Zurn:sha1:584405f7ccd4c8c0e63762e113f4650f2abd469e
The names are ambiguous. Rename them to make more sense.
Signed-off-by: Ophestra <cat@gensokyo.uk>
app: improve shim process management2025-04-06T18:55:17ZOphestracat@gensokyo.uk2025-04-05T14:51:39Zurn:sha1:e9a7cd526f4e5f0a8f7b18ad3682d2e3afbcb8ba
This ensures a signal gets delivered to the process instead of relying on parent death behaviour.
SIGCONT was chosen as it is the only signal an unprivileged process is allowed to send to processes with different credentials.
A custom signal handler is installed because the Go runtime does not expose signal information other than which signal was received, and shim must check pid to ensure reasonable behaviour.
Signed-off-by: Ophestra <cat@gensokyo.uk>