Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted #38

Open
ajabusch opened this issue Oct 8, 2020 · 0 comments
Open

Comments

@ajabusch
Copy link

ajabusch commented Oct 8, 2020

Hi I followed the instructions in the readme, but I got an error at

composer install 

within the container.

    PHP Fatal error:  Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/Solver.php on line 223

    Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/Solver.php on line 223

    Check https://getcomposer.org/doc/articles/troubleshooting.md#memory-limit-errors for more info on how to handle out of memory errors.

Setting
memory_limit = -1
in php.ini in the container might help, not sure where exactly, there isn no /etc/php...

My workaround was to execute "composer install" from the host inside the "back-end" folder

But then I got:

    Script cache:clear returned with error code 1
    !!  
    !!  In ArrayNode.php line 327:
    !!                                                                                 
    !!    Unrecognized options "dir_name, namespace" under "doctrine_migrations". Ava  
    !!    ilable options are "all_or_nothing", "check_database_platform", "connection  
    !!    ", "custom_template", "em", "factories", "migrations", "migrations_paths",   
    !!    "organize_migrations", "services", "storage".                                
    !!                                                                                 
    !!  
    !!  
    Script @auto-scripts was called via post-install-cmd

My workaround was to execute

    composer recipes:install --force -v
    composer install 

from the host inside the "back-end" folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant