V 4.0.0 consumes all RAM and freezes system

[marcomontevechi1]

Hello, im trying to get started so i followed initial steps to get to know the tool. So i did:

git clone --recurse-submodules https://github.com/React-Automation-Studio/React-Automation-Studio-Example-Project-1.git
cd React-Automation-Studio-Example-Project-1
 git checkout tags/V4.0.0

and git submodule status returns

b8ca936cd84e61f52c1c5e9ef733625ce81418b9 submodules/React-Automation-Studio (V4.0.0)

So all seems fine.

docker compose -f docker-compose-prod-with-demoioc.yml up --build

complains that there is no .env file or directory so i do

touch .env

and try again. After a few minutes my system freezes. I reboot it, start it again and try again this time with htop in another terminal. Htop shows that eventually all my ram (8 G) and swap partition (2 G) is consumed.
Can this be fixed?

[hanak]

Thank you for reporting the issue. May I ask you which OS you use as the host?
Are there any logs? The logs should appear in log/ (at least this happens when one runs docker-compose-dev.yml)?

[marcomontevechi1]

Im using Ubuntu 22.04.1 LTS with Docker version 20.10.18.

I ran the docker compose -f docker-compose-dev.yml up option and for some reason it worked without consuming all my RAM. I ran again now with the previous docker compose -f docker-compose-prod-with-demoioc.yml up --build and it worked. I suppose it used some cached images.

Should i close the issue? Are the logs still necessary?

[hanak]

Thank you for your comment and observation. I think it is quite tempting to close the issue. Yet, I am curious whether running docker compose -f docker-compose-dev.yml up fixed/added something docker compose -f docker-compose-prod-with-demoioc.yml up needed. It is a wild guess based on reading your latest comment. If you happen to have logs from the time of running docker compose -f docker-compose-prod-with-demoioc.yml up it would be great. If not, I will try to see whether I can get the same outcome as you when you reported the issue.

[wduckitt]

Hi, I think latest docker is building it all services in the compose file in parallel. The production frontend and style guide both need 4g ram each to build. Loading the Dev environment would only have built the production style guide. I think 8gigs RAM is at the limit. You could nurse the initial production build along by building just the frontend and then the style guide.

There is deprecated parallel option, perhaps setting to false might help:
https://docs.docker.com/engine/reference/commandline/compose_build/