Console Output

villars04 seems to be running inside container ec906afccf4ed2dc758b7f29a0cfcb6606f44d3fe70b21e43d9fffb40c412d64
$ docker run -t -d -u 0:0 -w /var/jenkins/workspace/adamantine-nightly --volumes-from ec906afccf4ed2dc758b7f29a0cfcb6606f44d3fe70b21e43d9fffb40c412d64 -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 ******** rombur/adamantine-stack:latest cat
$ docker top 6607b33ec0760bf741df5beec6c056c70c7c07be37ff4f75fc070a737ae871e5 -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=''`.