I'm finding that "docker --rm -v" does not work reliably when mapping in
a TDB database directory. The container is left running, seemingly in
some zombie state. This happen more often than not.
My guess is that some of mmap file clearup is still pending when the
process exits (or rather, the process becomes a linux zombie or
somesuch) and the container is not removable.
Whether this is a docker problem, a kernel problem or a fact of linux
life is not clear.
No --rm and an immediate "docker kill; docker rm" has worked each time.
(timing!)
I am running docker direct - no VM (I'm on a linux kernel on the hardware)
Has anyone else seen anything like this?
Andy