Console Output

fetnat_05 seems to be running inside container d365d04a6b4a55e28c8aa7298f8d7b4457bbb1cc1241fbc2baadaef88e123e59
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/ArborX_nightly --volumes-from d365d04a6b4a55e28c8aa7298f8d7b4457bbb1cc1241fbc2baadaef88e123e59 -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 ******** -e ******** -e ******** -e ******** index.docker.io/nvidia/cuda:12.4.1-devel-ubuntu22.04 cat
$ docker top 2489ae893186994bc8f92738ee915659b1d4c379e58fc96c267ce997a8c33dab -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=''`.