Console Output

fetnat03 seems to be running inside container 008fd7b1a637618e2701b88aa64cb68bdb5ac246efee4dc3ef3447b5a8f42e0c
$ docker run -t -d -u 0:0 -v /tmp/ccache:/tmp/ccache --env NVIDIA_VISIBLE_DEVICES=${NVIDIA_VISIBLE_DEVICES} -w /var/jenkins/workspace/ArborX_master --volumes-from 008fd7b1a637618e2701b88aa64cb68bdb5ac246efee4dc3ef3447b5a8f42e0c -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 ******** 93ec9112f15682c0665fae26b8d0f0bd908e5c1a cat
$ docker top 54de64fff74b97c6fbe8d5a83ce39bfd507bbbf743ee2228decb3cb00209deff -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=''`.