nohup strace -s 99999 -o ~/str_out.log q myprog.q 2>&1 > ~/q_out.log < /dev/null &
and you may be able to glean something useful in the run-up to the issue.
If it's not obvious already whether it's _really_ stuck, you could run a function within kdb on a timer (e.g. log a timestamp to disk), and see if that continues working. That might help narrow down the issue to the Docker (i.e. Linux conatainers) networking stack, and/or its signal-handling.
Tel: +44 (0)28 3025 2242
Tel: +1 (212) 447 6700
Tel: +61 (0)2 9236 5700