Skip to content

Console Output

Slave3 does not seem to be running inside a container
$ docker run -t -d -u 1000:1000 -v $HOME/.m2:/root/.m2:z -u root -w /home/cecaduser/workspace/MP_202530_G81_E3_MyWish_Back@2 -v /home/cecaduser/workspace/MP_202530_G81_E3_MyWish_Back@2:/home/cecaduser/workspace/MP_202530_G81_E3_MyWish_Back@2:rw,z -v /home/cecaduser/workspace/MP_202530_G81_E3_MyWish_Back@2@tmp:/home/cecaduser/workspace/MP_202530_G81_E3_MyWish_Back@2@tmp:rw,z -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 ******** citools-isis2603:latest cat
$ docker top 1de9dc19150a06181b4df209df289f8fe8e5f181c06597b4ef6e78c32636e68d -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=''`.