Console Output

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