Closed jcalahor closed 1 year ago
Hi @jcalahor , thank you for the feedback.
It looks like a common memory related problem with ec2 t2.micro: https://stackoverflow.com/questions/63171780/building-python-wheel-via-docker-compose-on-aws-ec2-gets-stuck https://www.reddit.com/r/aws/comments/6gvyoe/docker_container_seems_to_crash_my_ec2_instance/
Could you try to rebuild the image with less parallel jobs? I hope it might help to occupy less RAM during compilation. You need to clone the repo and then change some nums with any text editor:
Here you can see 8 - it's a number of parallel jobs, replacing 8->1 in these 3 places might help.
Could you also check what htop
shows during compilation? Interesting to see if it's a memory related problem indeed.
hi i tried reducing to 3 and same error, img as reference. i'm going to try locally ty
decided to try locally on my machine, (i don't want to try non free ec2 options), and so far it appears to be working, this issue can be closed thx for follow up
Is there an existing issue for this?
Current Behavior
docker compose is freezing see below when running. the machine i'm using is a ec2 machine: t2.micro
Expected Behavior
container should be able to be created
Steps To Reproduce
1) create a ec2: t2.micro machine 2) ssh from a client like mobaexterm or visual studio code 3) clone the code 4) perform docker compose -f docker/single-node/docker-compose.yaml up --build -d
BlazingMQ Version
1.0
Anything else?
No response