Console Output

fetnat05 seems to be running inside container df3a73e1fac55e6819601355e8f806f65a205884e4c4c5c3fee00d1856d1db97
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_PR-1104 --volumes-from df3a73e1fac55e6819601355e8f806f65a205884e4c4c5c3fee00d1856d1db97 -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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** celeritas/ci-jammy-cuda11:2023-08-02 cat
$ docker top 24cad8bdd92da4acb8457b4ef005dc632cd9b9049ec5696ef743f9e6016439d4 -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=''`.