5
2

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

More than 3 years have passed since last update.

Memory不足でElasticSearchのDockerコンテナ立ち上げが「exited with code 137」で終了したときの対応方法

Posted at

DockerでElasticSearchのコンテナを起動しようとしたら起動できなくて、「exited with code 137」というエラー文を吐いてて原因を調べてたら時間取られたのでメモ。

DockerでElasticSearchのコンテナを起動しようとしてエラー

$ docker-compose up <container名>
...
<container名> exited with code 137

原因

メモリの上限値が少ないからOut Of Memoryエラーになっているよう。
Dockerの初期設定のメモリは2GBになっているけど、ElasticSearchのコンテナはそれ以上にメモリ使うのかな。

cf. https://github.com/10up/wp-local-docker/issues/6

対応方法

Dockerのメモリ設定の上限値を上げる。2GBから8GBに上げたら起動できた。
(4GBでも起動できた)

Screen Shot 2020-03-24 at 17.10.44.png
5
2
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
5
2

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?