Console Output

fetnat05 seems to be running inside container 67a4f5ab8dcb94d4874ef050d80ae95217ebcef0902655364d2946d956f61bcb
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_develop --volumes-from 67a4f5ab8dcb94d4874ef050d80ae95217ebcef0902655364d2946d956f61bcb -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 6691e0e626d155643e497ef72e99a5113794cc098f74fca4c0d135822c3831e0 -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=''`.