微信公众号搜"智元新知"关注
微信扫一扫可直接关注哦!

App Engine部署作曲家的内存超出限制

如何解决App Engine部署作曲家的内存超出限制

最近除了app.yaml中的环境变量外,没有任何代码更改,在超过内存限制的云构建过程中,应用程序引擎部署失败,并且我不知道该在哪里更改或为什么会出现问题。我尝试设置“ gcp-build”以覆盖composer install命令,但是在云构建过程中出现此错误

Step #3 - "detector": ======== Output: google.PHP.composer-gcp-build@0.9.0 ========
Step #3 - "detector": unmarshalling composer.json: json: cannot unmarshal array into Go struct field     composerScriptsJSON.scripts.gcp-build of type string [id:070ec49f]
Step #3 - "detector": ======== Results ========

这是我的composer.json:

{
"name": "laravel/laravel","type": "project","description": "The Laravel Framework.","keywords": [
    "framework","laravel"
],"license": "MIT","require": {
    "PHP": "^7.2.5","doctrine/dbal": "^2.10","fideloper/proxy": "^4.2","fruitcake/laravel-cors": "^2.0","google/cloud": "^0.142.0","google/cloud-core": "^1.39","google/cloud-error-reporting": "^0.18.0","google/cloud-firestore": "^1.14","google/cloud-logging": "^1.21","guzzlehttp/guzzle": "^7.0.1","intervention/image": "^2.5","kreait/firebase-PHP": "^5.0","kreait/firebase-tokens": "^1.10","kreait/laravel-firebase": "^2.2","kyslik/column-sortable": "^6.3","laravel/framework": "^8.0","laravel/tinker": "^2.0","laravel/ui": "^3.0","owen-it/laravel-auditing": "^10.0","predis/predis": "^1.1","propaganistas/laravel-phone": "^4.2","superbalist/laravel-google-cloud-storage": "^2.2","tymon/jwt-auth": "^1.0"
},"require-dev": {
    "fzaninotto/faker": "^1.9.1","mockery/mockery": "^1.3.1","PHPunit/PHPunit": "^9.0","nunomaduro/collision": "^5.0"
},"config": {
    "optimize-autoloader": true,"preferred-install": "dist","sort-packages": true
},"extra": {
    "laravel": {
        "dont-discover": []
    }
},"autoload": {
    "psr-4": {
        "App\\": "app/","Database\\Factories\\": "database/factories/","Database\\Seeders\\": "database/seeders/"
    },"classmap": [
        "database/seeders","database/factories"
    ]
},"autoload-dev": {
    "psr-4": {
        "Tests\\": "tests/"
    }
},"minimum-stability": "dev","prefer-stable": true,"scripts": {
    "post-autoload-dump": [
        "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump"
    ],"post-root-package-install": [
        "@PHP -r \"file_exists('.env') || copy('.env.example','.env');\""
    ],"post-create-project-cmd": [
        "@PHP artisan key:generate --ansi"
    ],"post-install-cmd": [
        "Illuminate\\Foundation\\ComposerScripts::postInstall","composer dump-autoload","PHP artisan optimize","chmod -R 755 bootstrap\/cache","PHP artisan migrate  --no-interaction --force"
    ],"gcp-build": [
        "COMPOSER_MEMORY_LIMIT=-1 composer install --no-dev"
    ]
}

}

此外,在云构建期间收到此警告时,是否有机会将作曲家更新到v2:

Step #6 - "builder": Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2.0 is Now available and you should upgrade. See https://getcomposer.org/2

这是导致构建失败的实际问题:

Step #6 - "builder": Updating dependencies
Step #6 - "builder": 
Step #6 - "builder": Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleWatchGraph.PHP on line 52
Step #6 - "builder": 
Step #6 - "builder": Check https://getcomposer.org/doc/articles/troubleshooting.md#memory-limit-errors for more info on how to handle out of memory errors.Done "composer install --no-dev --no-progress --no-suggest --no-in..." (56.105751566s)
Step #6 - "builder": Failure: (ID: 5888fcc4) Loading composer repositories with package information
Step #6 - "builder": Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2.0 is Now available and you should upgrade. See https://getcomposer.org/2
Step #6 - "builder": Updating dependencies
Step #6 - "builder": 
Step #6 - "builder": Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleWatchGraph.PHP on line 52
Step #6 - "builder": 
Step #6 - "builder": Check https://getcomposer.org/doc/articles/troubleshooting.md#memory-limit-errors for more info on how to handle out of memory errors.

app.yaml中使用的运行时是PHP74,也试图将其更改为PHP72,同样的问题

解决方法

由于已部署的应用程序已经具有从App Engine部署生成的composer.lock文件,并且默认情况下,App Engine缓存提取的依赖项以减少构建时间。这将阻止您自动获取依赖关系的最新版本,并且会遇到错误:

您使用的是Composer的过时版本

要解决此问题,请在本地运行命令composer install,将依赖项固定到其当前版本,并在{strong}存在的情况下拥有composer.lockcomposer update 。然后使用命令“ gcloud beta app deploy --no-cache”进行部署,以安装依赖项的未缓存版本。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。