[anh79]

Hi @cpuguy83,

Thanks for your feedback. I couldn't gather enough information for bug reporting (But I had few rich logs that told "docker" has invalid memory access.)

As a work-around, I use a special patch of docker-compose that helps the containers to restart automatically when "docker" daemon restarts :)

> There's also been a known issue around creating lots of `docker exec` instances and those references not being released (so you can query for status later), this is also resolved.

Woh, this seems my case, though I am not sure about "releasing" (We run "exec" and "exit"; we don't hold any "exec" for longer than 2 seconds.) I haven't seen this mentioned in changelog (FIXME). Let me try again in ticket system!

[cpuguy83]

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]

Thanks 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 . Aanand Prasad has a better PR in https://github.com/docker/compose/pull/1754 (merged).