March-25th-2018, 05:25 PM
Well I never digged into detail what exactly the runtime deploys really in the container and which services are launched. Fact is that during deployment a lot of ssh services are used. Which one I don't know.
Since during my test everything worked fine when I made the video I did not spend any thought on it.
The only thing you see in the source code of the container is that it starts the runtime using the <i>/etc/init.d/codesyscontrol start &</i> construct in the <i>entrypoint.sh</i>. Use ps -A and you will see the following threads
root@6972b66c3ea6:/# ps -A
PID TTY TIME CMD
1 pts/0 00:00:00 entrypoint.sh
9 pts/0 00:00:00 tail
19 ? 00:00:00 sshd
159 pts/1 00:00:00 bash
167 pts/1 00:00:00 ps
Since during my test everything worked fine when I made the video I did not spend any thought on it.
The only thing you see in the source code of the container is that it starts the runtime using the <i>/etc/init.d/codesyscontrol start &</i> construct in the <i>entrypoint.sh</i>. Use ps -A and you will see the following threads
root@6972b66c3ea6:/# ps -A
PID TTY TIME CMD
1 pts/0 00:00:00 entrypoint.sh
9 pts/0 00:00:00 tail
19 ? 00:00:00 sshd
159 pts/1 00:00:00 bash
167 pts/1 00:00:00 ps
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)