Console Output

Slave1 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_E5_ViviendaUniversitaria_Back -v /home/cecaduser/workspace/MP_202530_G81_E5_ViviendaUniversitaria_Back:/home/cecaduser/workspace/MP_202530_G81_E5_ViviendaUniversitaria_Back:rw,z -v /home/cecaduser/workspace/MP_202530_G81_E5_ViviendaUniversitaria_Back@tmp:/home/cecaduser/workspace/MP_202530_G81_E5_ViviendaUniversitaria_Back@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 af544023cb61565035024b687d0c501e2dc2df109fabb7350510fce6e34c53c8 -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=''`.