Console Output

fetnat05 seems to be running inside container 848df06c8a1151342cc8e99325ec13ba3d639827de6ac0f8ac5b062a23ca6081
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_PR-1034 --volumes-from 848df06c8a1151342cc8e99325ec13ba3d639827de6ac0f8ac5b062a23ca6081 -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 40c6a1089ff2816304dc7672b2ea4e097bb4f3ea402f4393362e2213d696287c -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=''`.