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
dgraph fails silently when OOM under docker/Mac #1989
Milestone
Comments
I have been investigating this. This is the default behaviour of Docker. To confirm that the container was killed due to OOM, the stopped container can be investigated as mentioned at https://stackoverflow.com/questions/38112968/how-to-know-the-reason-why-a-docker-container-exits. |
Same on a GKE instance (2 vCPUs and 13GB RAM... 8 hours for nothing 👎) Ended with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is not a bug on itself as it is related to moby/moby#21083 but given the memory requirements of dgraph, it might be hit by other users.
If you suspect this could be a bug, follow the template.
1.0.1
Yes
Ram: 16G, macOS 10.13.2, docker 17.12.0-ce-rc4-mac44
Using docker-compose (https://gist.github.com/llonchj/a927620b75a5766ac71aeff6501f2b02).
https://gist.github.com/llonchj/a172ab07547e296f07d670799c69152d
It works when running natively on the mac, but as per moby/moby#21083 fails when runs in a container.
The text was updated successfully, but these errors were encountered: