4 ms·
Yes, it's docker that was holding on to these exec instances (and cluttering up the `docker inspect` output if you do a bunch). We now do GC on these. ps, you
by cpuguy83 11y ago
Yes, it's docker that was holding on to these exec instances (and cluttering up the `docker inspect` output if you do a bunch).
We now do GC on these.
ps, you can add `reastart: always` to your compose file, and docker daemon will automatically restart those containers for you.
- anh79 11y agoThanks a lot. I wonder why this is not mentioned in the changelog :) Regarding the `docker-compose` issue, it's described here https://github.com/docker/compose/pull/1723 https://github.com/docker/compose/pull/1723 . Aanand Prasad has a better PR in https://github.com/docker/compose/pull/1754 https://github.com/docker/compose/pull/1754 (merged).