## Summary The `configure` checks for `nvidia-container-cli` and presencs of nVidia libraries might also be considered "impolite". On a Gentoo system compiling charliecloud in a sandbox, I get the sandbox violation: ``` VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: fopen_wr_creat S: deny P: /proc/self/task/972/comm A: /proc/self/task/972/comm R: /proc/971/task/972/comm C: nvidia-container-cli list ``` triggered by the call to `nvidia-container-cli list`. In addition to this, the check fails with insufficient permissions in a compile sandbox: ``` nvidia-container-cli: initialization error: nvml error: insufficient permissions ``` Version: 0.44 (but also earlier) Environment: Gentoo Linux with nVidia graphics and `nvidia-container-toolkit` installed. ## Steps to reproduce 1. Run `./configure` in a [sandboxed](https://wiki.gentoo.org/wiki/Project:Sandbox) environment, and have `nvidia-container-cli` installed (note: also works, or rather fails, as unprivileged user). 2. Observe sandbox violation. 3. If build user has not actual GPU access (e.g. can not access `/dev/nvidiactl`), also observe "insufficient permissions" error. (note: I only see this now as I did not have nvidia-container-cli installed previously) ## Expected behavior Check can be disabled, e.g. as part of impolite checks :wink: . ## Actual behavior Check is always executed. ## Comments The checks are of course fine in "regular" environments when compiling as user, but might break when compiling in a system with `nvidia-container-cli` installed but no GPU access or a sandbox preventing unusual modifications of task `comm` names, as `nvidia-container-cli` sadly does. So it would be great if these checks (which only affect execution of tests) could be disabled for sandboxed builds or builds as users without actual GPU access.