Console Output

fetnat03 seems to be running inside container 4ba416fa14a4f52b4031542a3d0260389a58eb42718df7cea7202d2f594438ad
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_PR-1065 --volumes-from 4ba416fa14a4f52b4031542a3d0260389a58eb42718df7cea7202d2f594438ad -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 df860e583d546ea3e9b83fba6aa0946a440e8b76037a098761c944079e4a7240 -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=''`.