From 74cc5e2041a2c32e1824b32316bd95f2c8a811f5 Mon Sep 17 00:00:00 2001 From: Daan De Meyer Date: Tue, 13 Aug 2024 10:36:40 +0200 Subject: [PATCH] docs: Mention the new mount API in the container interface doc Let's mention that the new mount API may be used to establish new mounts in a container without needing the /run/host/incoming directory. --- docs/CONTAINER_INTERFACE.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/CONTAINER_INTERFACE.md b/docs/CONTAINER_INTERFACE.md index e64953c8b4..e20c76d900 100644 --- a/docs/CONTAINER_INTERFACE.md +++ b/docs/CONTAINER_INTERFACE.md @@ -237,7 +237,9 @@ care should be taken to avoid naming conflicts. `systemd` (and in particular directory: it's used by code outside the container to insert mounts inside it only, and is mostly an internal vehicle to achieve this. Other container managers that want to implement similar functionality might consider using - the same directory. + the same directory. Alternatively, the new mount API may be used by the + container manager to establish new mounts in the container without the need + for the `/run/host/incoming/` directory. 2. The `/run/host/inaccessible/` directory may be set up by the container manager to include six file nodes: `reg`, `dir`, `fifo`, `sock`, `chr`,