Console Output

fetnat05 seems to be running inside container b3517e93f044dd7efc194e11e91b888823fb4a8cdd0e088a697c6f6654c71052
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/celeritas_backports_v0.4 --volumes-from b3517e93f044dd7efc194e11e91b888823fb4a8cdd0e088a697c6f6654c71052 -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 058e7c3d90b6be36882518a0b8f35b34c7847953c3a7e6c36c4b4e2c700bcb49 -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=''`.