Container with MySQL crash almost every day about mysql HOT 7 CLOSED

If you run docker logs mysql-container you'll get the MySQL log. Probably only the last bit is really relevant (which you can get with something like docker logs --tail=100 mysql-container). My hunch would be that you're running out of RAM, but it's hard to say for sure.

from mysql.

I've been using docker logs mysql-container but i didn't see anything.

I'm now monitoring RAM consumption more thoroughly to see if the problem is the lack of RAM in my machine.

Thank you

from mysql.

When you say crashes, what do you mean. Are you getting an error connecting to it?

from mysql.

The container suddenly stops working. If you look at the logs nothing appears.

I'm with tianon that is lack of RAM problem.

from mysql.

I've experienced precisely the same problem and it was due to a RAM constraint. The application I run typically consumes fairly little RAM (~200MB) but bursts periodically up to over 500MB. During these bursts, the MySQL container (which consumed ~470MB) would consistently crash. As my host only had 1GB total RAM, bumping up to 2GB has so far resolved the issue.

Not sure if this is an issue with this image in particular, but it was difficult to track down. In fact the RAM issue only "clicked" while I happened to glance at top during one of the bursts I described above... 😢

from mysql.

the default settings of MySQL can be quite memory-hungry. While great for performance, depending on your use case (and environment), you may have to tweak the settings (I.e running with your own configuration file); for an earlier discussion on this, see #3

from mysql.

Since this issue appears to be untouched, and as mentioned in #3 , related to the the underlying system instead of an issue with the image, I am closing this.

In the future, these sorts of questions/requests would be more appropriately posted to the Docker Community Forums, the Docker Community Slack, or Stack Overflow.

from mysql.