Currently the sembench process runs once (or brutaly fails at it) and then exits.
This leaves the docker-container inaccesible for further inspection through docker exec -it «myname_kgap_sembench» /bin/bash
There seems to be a --attach flag to docker compose up that can relaunch a certain container -- but that feels like it would just end up existing also?
Anyway, we should investigate and document how docker might allow the required inspection?
If not, we could also introduce an env variable that enables the container to keep running (inside the python or in a surrounding shell script) so the extra connect with docker exec can be executed?
Currently the sembench process runs once (or brutaly fails at it) and then exits. This leaves the docker-container inaccesible for further inspection through
docker exec -it «myname_kgap_sembench» /bin/bash
There seems to be a
--attach
flag todocker compose up
that can relaunch a certain container -- but that feels like it would just end up existing also?Anyway, we should investigate and document how docker might allow the required inspection?
If not, we could also introduce an env variable that enables the container to keep running (inside the python or in a surrounding shell script) so the extra connect with
docker exec
can be executed?