Console Output

fetnat04 seems to be running inside container 53ac5b34a5db103fd8ae8e843ba04c4749e3d530685eaaf04951e02605ae086b
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/ArborX_nightly --volumes-from 53ac5b34a5db103fd8ae8e843ba04c4749e3d530685eaaf04951e02605ae086b -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** nvidia/cuda:12.2.0-devel-ubuntu22.04 cat
$ docker top e35f820fa8c60575af7b1b9e274e1500a30e4209aee382f72e9b9f64167317c6 -eo pid,comm
ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).
Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.