Console Output

fetnat03 seems to be running inside container 03b7bae10d390ea917e8c6db2dac4c5d6bd4b305625b8340884716f2cf528a9a
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_develop --volumes-from 03b7bae10d390ea917e8c6db2dac4c5d6bd4b305625b8340884716f2cf528a9a -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 ceb78db0905b210ad99b5a4197ab4e66c8be5774fdabde7353c4b1ae72efcfb4 -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=''`.