July-4th-2018, 09:15 AM
Hello Frank,
it seems you are not familiar in all details with Docker and containers and how they start.
A container always has an entrypoint ... in this entrypoint you specify a single file that Docker is calling when the container is started. This start file is running as PID 1 process in the container. If you call the vhusbdarm service as background process as you do it, the script file itself will exit and since the script file is PID 1 the complete container will be stopped by Docker cause there is no PID 1 any more.
Two possibilities:
1. run vhsubdarm not as a background serving
2. or you program a while loop at the end of your script like we did it in this example here https://github.com/Hilscher/netPI-blueto...rypoint.sh
it seems you are not familiar in all details with Docker and containers and how they start.
A container always has an entrypoint ... in this entrypoint you specify a single file that Docker is calling when the container is started. This start file is running as PID 1 process in the container. If you call the vhusbdarm service as background process as you do it, the script file itself will exit and since the script file is PID 1 the complete container will be stopped by Docker cause there is no PID 1 any more.
Two possibilities:
1. run vhsubdarm not as a background serving
2. or you program a while loop at the end of your script like we did it in this example here https://github.com/Hilscher/netPI-blueto...rypoint.sh
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)