fn exit_like_bwrap_without_namespaces(reason: &str) -> !Expand description
Exits the way bubblewrap exits when it cannot create its namespaces.
A supervisor cannot start under another tracer or another listener, nor
on a host that refuses it access to its own child. Inside proot-next
the first never happens, since an exec of bwrap is served as a nested
launch (see exec::nested); otherwise the caller is a program that
started us as bubblewrap, and those programs know this message (GTK’s
glycin runs its image loaders unsandboxed on seeing it).
§Arguments
reason- Why proot-next cannot start, appended to the message.