Console Output

fetnat05 seems to be running inside container 95221f7f44dbfd8aa2556518dad5933d6cc82910264f8f18707f26d44d231d30
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_PR-1053 --volumes-from 95221f7f44dbfd8aa2556518dad5933d6cc82910264f8f18707f26d44d231d30 -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 e8850c718fb09c7165ec4126136e2d99d6b4ac7d8718b5c45eae7259f5bd9171 -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=''`.