简体   繁体   中英

git push fails with a memory error in a large repo when using GitHub checkout actions in a Kubernetes pod

We have a Public API that includes a nightly metadata updater run via Cron in a pod deployed with Github Actions and Kube.netes . 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.

After using git fetch --unshallow the pod was able to complete a git commit and git push to re-deploy itself.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM