---
title: "Why does my Next.js build fail with a \"Bus error (core dumped)\" when I push my node_modules folder to my repository?"
date: "2025-05-08T05:14:03+00:00"
summary: "Discover why Next.js builds fail with \"Bus error\" when pushing node_modules. Learn about architecture mismatches and how to resolve them."
image:
type: "article"
url: "/acquia-cloud-platform/add-ons/node-js/help/68636-why-does-my-nextjs-build-fail-bus-error-core-dumped-when-i-push-my-nodemodules-folder-my-repository"
id: "09fb53ca-877e-4aee-8960-3ca4c762cbcf"
---

The "Bus error (core dumped)" arises from an architecture mismatch. When you install dependencies (using npm install) on a machine with one CPU architecture, such as ARM , and then push the resulting node\_modules folder to your repository, that folder contains packages compiled for that specific architecture.   
  
When another machine with a different CPU architecture, such as AMD64/x86\_64, that we use for code deployments clones the repository and attempts to build, these pre-compiled binaries within node\_modules are incompatible. This incompatibility results in the operating system to generate the "Bus error."   
  
Next.js itself does not provide a more detailed error message in this case because the failure stems from the OS's inability to execute the incompatible native code.  
  
If you must push the node\_modules folder to your repository, build your code using an AMD64 architecture machine for compatibility.