Open frottke opened 1 day ago
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
Note: You can give me feedback by 👍 or 👎 this comment.
memoryLimit": "0G",
?
Shouldn't that be 10G?
It was intentional 0G to avoid the default value 8G from AL-Go. 0G with process isolation is "dynamic". Which means using the limit of the host os. Worked perfectly :)
OK - when using process isolation, the default should be "no memorylimit", hence "memoryLimit 0G" shouldn't be needed. When using hyperv - you need to set a maximum memory limit to make this work.
You should be able to create a settings file called .github/localdevenv.settings.json - which will only be applied during localdevenv and hence will not be applied during CI/CD.
and... reading your issue again - you already have this settings file.
Hi Freddy,
first of thank you for fixing #3718! :)
Resulting from #3718 we are now using HyperV-Isolation but unfortunately we now get a new error. This error was originally the reason to switch to process isolation a few months ago.
Thrown Error
Scripts used and config via AL-Go to create container and cause the issue
localDevEnv.settings.json
When changing memoryLimit to for example 16G it does work. When using process isolation the value "0G" was the solution that bccontainerhelper used the default which was perfect for our needs instead of the default value of AL-Go (8G) which is not sufficient for the installation of the dependencies ( around nine apps). Is there a "better" solution then setting it to 16GB?
Full output of scripts