Open 0Nel opened 1 year ago
You can test this with the default images and the example startscript. Setting verbose to true makes the location of the error quite obvious.
In the release build phase, we tell the container it is initialized, so it doesn't change dockerusers uid to the host uid.
The entrypoint checks for the file and if it in not existing, it will chnage the uid and exit to have the uid set on the next run: https://github.com/dfki-ric/docker_image_development/blob/master/image_setup/01_base_images/entrypoint.bash#L81 https://github.com/dfki-ric/docker_image_development/blob/master/image_setup/01_base_images/entrypoint.bash#L102
I guess in release mode the contaienr does not exit on the first run, but the script expects it to exit once and restarts the container:
Can you test: https://github.com/dfki-ric/docker_image_development/pull/70 ?
Executing the example startscript in devel mode works fine. However for release mode you get into the container first and the startscript is only executed once you try to exit the container. I noticed this in the corobx project already, but didnt find the time to look into it up until now.
I can pinpoint the location of the error, but have no idea, why it occurs. The issue is that the
docker run ...
line within thegenerate_container
function in thedocker_commands.bash
file won't exit automatically. I already checked all passed arguments, but did not yet figure out why this is happening. I suspect it to be related to the entrypoint.sh somehow. Any idea?