Unfortunately the link provided is to a private log. However, based on the section posted here the following from a thread on the same topic is relevant
If this doesn’t help, there are several other posts referring to code 137 that may.
Thanks @coelmay. I’ve copied the log file to a gist and I don’t see any obvious hints as to the cause. I was able to build/deploy earlier today on Gatsby v3 maybe the v4 changes the memory usage(?)
Thanks again @coelmay. I’ve removed the obsolete plugin from my netlify.toml and enabled the Essential Gatsby Plugin in the dashboard. But no change in the build
My site has 1600 pages and does run some big queries to build index pages, glossary, and summary pages automatically so maybe it’s just too big for the free plan?
I’m thinking I may need to configure Gatsby Cloud to build and then deploy to Netlify instead of trying to build directly on Netlify(?)
Thanks for your patience here! Are you still encountering this obstacle? If so, could you please attempt installing Docker image? Once that is installed, please try building locally and see if this helps.
Thanks for your patience here! Are you still encountering this obstacle? If so, could you please attempt installing Docker image? Once that is installed, please try building locally and see if this helps.
@hillary the instructions for the docker image seem contradictory: Using our tool from the base of a checkout of our build-image repository, Run the image in interactive mode, mounting your repository as a volume: ./test-tools/start-image.sh path/to/my/repo
Since I ran docker pull I don’t have a local checkout of the build-image repo… (and don’t know where to pull it from).
Is there a specific way I should run the docker image?
docker run -it netlify/build just puts me in / and I don’t see any start-image.sh script?
~/dev > docker run -it netlify/build
buildbot@9de544f144b6:/$ ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var
Thank you for the feedback about the build image docs. We’d try to get some eyes on that.
About your issue, that does seem like the build is running out of memory and sadly there’s no easy fix for it, if at all there’s one. In my experience Gatsby has usually been slower and took more resources than a lot of other site builders, so that fact that you’re failing to build 1600 pages does make sense. Now what you can do about this? Not much actually, but if you want to be 100% sure this is a memory issue, you can try upgrading the memory configuration of the build image that you’re trying locally. If the build works at certain available RAM, you can be sure it’s a RAM issue. If the build always fails no matter what, that’s a different story. But in the first case, you might have to continue building locally and deploy it via CLI.
On the enterprise plan, there’s a HP Build addon that has much more powerful build systems.
This my personal blog so I’ll either keep building/deploying from my local machine. Or go “hybrid” and build on Gatsby and have them deploy to Netlify (I might be locked in from using the Netlify smart url feature).