resolve_self
Diagnostic `nanook::cli::resolve_self`
Summary
could not resolve the running nanook binary: {0}
Help
pass an explicit --path <binary> so the command doesn't depend on std::env::current_exe
Details
When this fires
nanook self verify or nanook self sign was invoked without --path, so the command tried std::env::current_exe to locate the running binary, and that call failed. This is rare on healthy systems; usual roots are running nanook through a fexecve-style loader that does not register the executable, running on a minimal container without /proc, or having HOME unset for the sign helper that looks up a default signing key.
What to check
Pass --path so the command does not depend on environmental lookup:
If $HOME is the missing piece, set it before invoking the command, or supply --key explicitly.