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 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-