Console Output

fetnat05 seems to be running inside container 5acf70f3f14f6576018e1001af243532f02bedffe013a746c2d6822a0a781224
$ docker run -t -d -u 0:0 -v /tmp/ccache:/tmp/ccache --env NVIDIA_VISIBLE_DEVICES=${NVIDIA_VISIBLE_DEVICES} -w /var/jenkins/workspace/ArborX_PR-1082 --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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** 72c16c22ea64882c61b41a3641805d0197497ae4 cat
$ docker top 7606390325c960fb05288085a002be3af52ef32ae495794d023ce2059798c8a4 -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=''`.