Memory issues can be caused by a number of things.
There's been a lot of work done to improve some leakages around the logging -- both by being able to disable logging if you don't need it or switch to a different logger, and general improvements to the default jsonlog logger.
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.
It would be awesome if you could profile it and submit a bug report with how you are using docker and where you are seeing memory growth.
Let me know how I can help so we can get this resolved.
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!
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.
It would be awesome if you could profile it and submit a bug report with how you are using docker and where you are seeing memory growth. Let me know how I can help so we can get this resolved.