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 c8aee5d38639484a30b7607ba6c4b06ce98b6b52d122b848984f89ec4996417d -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=''`.