Skip to content
Back

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

  • 0
  • 4
  • 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 but deployment fails because the sidecar expects code.tar.gz while the builder produces code.sqfs. The team applied a fix, so try again and confirm if the issue is resolved.
9 Jul, 2026, 09:43

That definitely looks more like a packaging mismatch than a Next.js build issue. Since the builder is producing a .sqfs archive while the sidecar is still expecting code.tar.gz, I'd verify whether this started after a recent Appwrite runtime update. Are you seeing this across all deployments or just this specific project? <@475506683381022721>

9 Jul, 2026, 09:51

this is happening to multiple people, so I'd say it's definitely not a specific project

9 Jul, 2026, 09:51

A computer science university student

9 Jul, 2026, 09:52

Almost graduated, one course left 🙂

9 Jul, 2026, 09:53

How old?

9 Jul, 2026, 09:53

31, took my time haha

9 Jul, 2026, 10:14

<@475506683381022721> <@944857172196589659> <@194949135231614978> our team have applied a fix, please try now, and confirm if this has been resolved

9 Jul, 2026, 10:25

Worked for me

9 Jul, 2026, 10:26

Thanks

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