Console Output

fetnat05 seems to be running inside container e04395048aba2c0a0ce57c67f6605fa31a76e2fa45982371da926c593de7e74c
$ 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 e04395048aba2c0a0ce57c67f6605fa31a76e2fa45982371da926c593de7e74c -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 e5011516f332246b0ac51bced1dc664b4b0c15f852b7c0267d302ebcef5e6a46 -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=''`.