Console Output

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