Console Output

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