This "workaround" (work around what) prevents a graceful shutdown of the container because the root process never ends - although the database was already shut down. T. m.,
docker stop -t 200 oracle-xe
takes always 200 seconds, even if the database shutdown only needs 30 seconds or so. After the timeout of 200s the container is killed.
This means that also a shutdown of docker (and therefore the complete workstation) takes at least 200 sec - at least if the timeout was defined by docker run --stop-timeout 200 ...).
Removing the tail-Statement solves that problem. Seems to bring no other problems.
The last lines of
runOracle.share:This "workaround" (work around what) prevents a graceful shutdown of the container because the root process never ends - although the database was already shut down. T. m.,
takes always 200 seconds, even if the database shutdown only needs 30 seconds or so. After the timeout of 200s the container is killed.
This means that also a shutdown of docker (and therefore the complete workstation) takes at least 200 sec - at least if the timeout was defined by
docker run --stop-timeout 200 ...).Removing the
tail-Statement solves that problem. Seems to bring no other problems.