Console Output

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