在 Kubernetes pod 中使用 GitHub 签出操作时，git Push 失败，并在大型存储库中出现内存错误
我们有一个 公共 API，其中包括每晚的 公共 API。 com/ACMILabs/acmi-api/blob/main/scripts/update-api.sh" rel="nofollow noreferrer">元数据更新程序 通过 Cron 在使用 Github 操作 和 Kubernetes。一夜之间，更新程序从我们的私有 API 中提取新的元数据，然后提交这些更改并将它们推送到自身以刷新 Github 存储库并触发 lint/测试/构建/部署。
我们使用 actions/checkout 默认情况下获取单个提交。
在更新了约 43,000 条记录约 700mb 存储库几周后，我们开始在 git Push 步骤中看到失败：错误：pack-objects 死于信号 9
Enumerating objects: 11754, done.
Counting objects: 100% (10881/10881), done.
error: pack-objects died of signal 9
error: pack-objects died of signal 9
error: remote unpack failed: eof before pack header was fully read
增加 pod 资源 没有帮助。
We have a Public API that includes a nightly metadata updater run via Cron in a pod deployed with Github Actions and Kubernetes. Overnight the updater pulls fresh metadata from our private API, and then commits those changes and pushes them to itself to refresh both the Github repo and trigger a lint/test/build/deployment.
We're using actions/checkout which fetches a single commit by default.
After a few weeks of updating our ~43,000 record ~700mb repo we started seeing failures at the git push step: error: pack-objects died of signal 9
Enumerating objects: 11754, done.
Counting objects: 100% (10881/10881), done.
error: pack-objects died of signal 9
error: pack-objects died of signal 9
error: remote unpack failed: eof before pack header was fully read
Increasing pod resources didn't help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用 git fetch --unshallow 后，pod 能够完成 a
git commit和git push到重新部署自身。After using
git fetch --unshallowthe pod was able to complete agit commitandgit pushto re-deploy itself.