Skip to content
Back

Build succeeds but deployment fails — sidecar expects code.tar.gz, builder produces code.sqfs

  • 0
  • 1
  • Sites
  • Web
8 Jul, 2026, 22:06

My Next.js 15.5.20 site (standalone output mode) builds successfully on Appwrite Sites, but the deployment fails at the final packaging step with:

[sidecar:build] Build archive was not created at /mnt/code/code.tar.gz The build log shows the open-runtimes builder chose squashfs as the packaging format:

[open-runtimes] Auto compression: squashfs Creating 4.0 filesystem on /mnt/code/code.sqfs, block size 1048576. The builder completed everything correctly — compiled the app, detected the standalone build, bundled for SSR, and created the squashfs archive. But the sidecar is looking for a .tar.gz file that was never created.

Steps to reproduce:

Deploy a Next.js 15.5.20 app with output: "standalone" in next.config.ts Build completes successfully (all pages generated, no errors) Deployment fails with the code.tar.gz not found error Relevant log sequence:

[open-runtimes] Detected standalone Next.js build. [open-runtimes] Bundling for SSR started. [open-runtimes] Bundling for SSR finished. [open-runtimes] Auto compression: squashfs [open-runtimes] Build packaging finished. [open-runtimes] Build cache saved. [open-runtimes] Build finished. [sidecar:build] Build archive was not created at /mnt/code/code.tar.gz Expected behavior: The sidecar should recognize the squashfs archive produced by the builder, or the builder and sidecar should agree on the same packaging format.

Environment:

Framework: Next.js 15.5.20 Output mode: standalone Platform: Appwrite Cloud (Sites)

TL;DR
Build succeeds on Appwrite Sites for Next.js app with standalone output, but deployment fails because sidecar expects a code.tar.gz file while the builder produces a code.sqfs file due to compression in squashfs format. The issue lies in the mismatched packaging formats. To resolve, either adjust the sidecar to recognize squashfs archives or ensure both builder and sidecar use the same packaging format.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more