Skip to content

Commit 5f0c1c4

Browse files
DaanDeMeyerbluca
authored andcommitted
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. (cherry picked from commit 74cc5e2) (cherry picked from commit 65eff44) (cherry picked from commit 53d92de) (cherry picked from commit c12ef9e) (cherry picked from commit 778f622)
1 parent 5d5f712 commit 5f0c1c4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/CONTAINER_INTERFACE.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,9 @@ care should be taken to avoid naming conflicts. `systemd` (and in particular
230230
directory: it's used by code outside the container to insert mounts inside
231231
it only, and is mostly an internal vehicle to achieve this. Other container
232232
managers that want to implement similar functionality might consider using
233-
the same directory.
233+
the same directory. Alternatively, the new mount API may be used by the
234+
container manager to establish new mounts in the container without the need
235+
for the `/run/host/incoming/` directory.
234236

235237
2. The `/run/host/inaccessible/` directory may be set up by the container
236238
manager to include six file nodes: `reg`, `dir`, `fifo`, `sock`, `chr`,

0 commit comments

Comments
 (0)