Console Output

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