I'm using - image: peopleperhour/dynamodb
for a docker image in my CircleCI config file.
In CircleCI it's outputting the following.
Initializing DynamoDB Local with the following configuration:
Port: 8000
InMemory: false
DbPath: /var/dynamodb_local
SharedDb: false
shouldDelayTransientStatuses: false
CorsParams: *
Exited with code 137
The first tests pass fine and Exited with code 137
doesn't happen until later on. But once that error happens all the tests start failing.
I saw this link and changed my code to the following with no luck.
- image: peopleperhour/dynamodb
environment:
MAX_HEAP_SIZE: 2048m
HEAP_NEWSIZE: 512m
Any ideas on how to fix this?
davidmerrick :
I ran into the same issue. I ended up just using localstack for it, as the memory footprint seems to be lower.\n\nMy config for that container looks like:\n\n- image: localstack/localstack\n environment:\n SERVICES: dynamodb:4570\n DEFAULT_REGION: us-west-2\n",
2019-07-30T00:33:04
yamenk :
As a workaround, you can try to specify a restart policy for the container:\n\n- image: peopleperhour/dynamodb\n restart: on-failure # Restart the container if it exits due to an error\n environment:\n MAX_HEAP_SIZE: 2048m\n HEAP_NEWSIZE: 512m\n",
2017-08-24T16:05:25
Stephen Lester :
You can try 3 other things. \n\n1:\n\nAdd resource limits to your docker section of the config.yml\nresources:\n\n requests:\n memory: \"2Gi\"\n limits:\n memory: \"4Gi\"\n\n\nThe default resource is Medium with 2 vCPUs and 4GB of ram.\n\n2:\n\nUse Java option environment vars to set memory limits.\nhttps://circleci.com/blog/how-to-handle-java-oom-errors/\n\n3:\n\nIf you are using a non-basic account you can tell Circleci to use a different machine resource_class. You have to have the performance plan for this.\nhttps://circleci.com/docs/2.0/configuration-reference/#resource_class",
2019-09-20T19:33:08