Inconsistency in docker-compose due to crapi-identiy low memory limit

[willmccardell]

When I run the docker-compose command listed in the readme across 3 different machines, the instructions provided do not work. In many of the cases, I was seeing different errors each time, but lately it's been a fairly standard error:

crapi-identity exits with status code 137.

As you can see, crapi-identity finishes starting, but then crashes later on.

output of docker logs:

I was able to get the docker-compose command to finish twice out of maybe 60 attempts, so while it won't always fail, it almost always does.

Platforms tested on, all 64 bit:

• AWS Linux
• Ubuntu hosted in AWS, fresh instance spun up entirely for this debugging.
  ** Linux redacted 5.15.0-1004-aws Profile Picture image not loading on Community Forum #6-Ubuntu SMP Thu Mar 31 09:44:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
• Kali Linux VM hosted on Windows
  ** This was the host that docker-compose finished twice on.

This error occurred on both the main and develop branches.

Steps to reproduce:

• Create an Ubuntu t2.micro in AWS or equivalent.
• Run the steps listed in the README under the Docker Quick Start section to reproduce.

This problem is similar to #9.

After a lot of troubleshooting, I determined that updating the max memory limit for the crapi-identity to be 384M from 256M gave it enough headroom to consistently start and run the crapi-identity container.

Originally posted by @willmccardell in #54 (comment)