-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transparent Huge Pages support should be disabled #191
Comments
See #55 (comment), #19, and #35 You might also like this comment in particular #55 (comment) |
@wglambert Ah, so this is a Docker Mac VM thing, got it, I should've searched the closed comments. |
Hi everybody, Just to understand..
So I have 3 warnings (besides the lack of the config file) related to:
Finally I was able to fix those warning with the following actions (read from various GH issues):
But I wanted to be sure.. I saw GH issues referring to them as if there are all related but it doesn't seem so.. Do these fixes are the right ones, or are they only some workarounds? Regarding the issue 2. since it is also related to Regarding 3. since I saw some people running these commands in the container (if I'm not mistaken) so could it be possible to somehow embed those fixes in the image (docker-compose or a dockerfile). Thank you very much. |
@sanjibukai The best solution I've found for 1), and 2) is to simply set them in the compose file:
and it's my understanding that handling 3) in some way, would require running the container as privileged, giving it access to the host, which isn't the best security idea. Note: I would hesitate to follow |
I am running Docker on a latest-gen Mac OS X laptop with 32GB of RAM, 6.0GB allocated to Docker. I have a Dockerfile that is simply copying a file with our custom config:
I then use a mounted volume, and grab the latest snapshot redis
dump.rdb
file from one of our production machines, place it in the mount, then start up redis. This had been working fine, until recently, the dump file is now 1.9GB and upon running the container, it hangs for awhile, clients getand then after maybe 2-3 minutes of fan spinning, we get
At this point the Redis container is exited. Running
docker logs redis
gives:Is this something that you can update in the Docker image? Or a Mac OS X (host) thing? Or is the error a false positive?
The text was updated successfully, but these errors were encountered: