You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
runtime-linux: Condition /proc/self/fd symlinks on source existence
Since 279c3c0 (linux: relax filesystem requirements for container,
2017-01-23, #666) it's no longer guaranteed that /proc will exist.
And there doesn't seem to be much point in requiring symlinks which
will be known broken.
This commit also tightens the timing. Before it was just "after the
container has `/proc` mounted", which could have happened during the
'delete' operation (if the container authors wanted to be especially
ornery). With this commit, I've put the creation in step 2 of the
lifecycle. And within step 2, it happens after 'mounts' has been
processed.
Signed-off-by: W. Trevor King <[email protected]>
Copy file name to clipboardExpand all lines: runtime-linux.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Some of the file descriptors MAY be redirected to `/dev/null` even though they a
8
8
9
9
## <aname="runtimeLinuxDevSymbolicLinks" /> Dev symbolic links
10
10
11
-
After the container has `/proc` mounted, the following standard symlinks MUST be setup within `/dev/` for the IO.
11
+
While creating the container (step 2 in the [lifecycle](runtime.md#lifecycle)), runtimes MUST create the following symlinks if the source file exists after processing [`mounts`](config.md#mounts):
0 commit comments