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_202510_G81_E1_AdopcionMascotas_Back -v /home/cecaduser/workspace/MP_202510_G81_E1_AdopcionMascotas_Back:/home/cecaduser/workspace/MP_202510_G81_E1_AdopcionMascotas_Back:rw,z -v /home/cecaduser/workspace/MP_202510_G81_E1_AdopcionMascotas_Back@tmp:/home/cecaduser/workspace/MP_202510_G81_E1_AdopcionMascotas_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 1bb84e35e8f5d6e8404387b833bd6c3902886c8c08566544887295ea01fdfb9b -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=''`.