Console Output

fetnat05 seems to be running inside container 460c7040903f09977fd73cffdf142fc8a5a3a252df2d4201a4152ff03c9c870f
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_PR-1073 --volumes-from 460c7040903f09977fd73cffdf142fc8a5a3a252df2d4201a4152ff03c9c870f -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 4db44d14f710c21098dc2f35e193c383a654505d0408d0e0d95104e6bbbd3f2f -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=''`.