Increased memory limit for crapi-identity container #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Pull request to fix #56 . This will make it more likely for docker-compose to work to start the crAPI services.
Initially I fixed this with 512M, but since the original limit was 256M I changed it to 384M just to keep it lighter weight.
Testing
Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested the service locally.
Testing involved 2 different machines, one local VM and one VM in AWS.
Steps taken to test:
Repeated the docker-compose down then docker-compose up commands a few times to on each machine to ensure it wasn't a fluke.
Checklist: