Build succeeds but deployment fails — sidecar expects code.tar.gz, builder produces code.sqfs
- 0
- 4
- Sites
- Web
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)
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>
this is happening to multiple people, so I'd say it's definitely not a specific project
A computer science university student
Almost graduated, one course left 🙂
How old?
31, took my time haha
<@475506683381022721> <@944857172196589659> <@194949135231614978> our team have applied a fix, please try now, and confirm if this has been resolved
Worked for me
Thanks
Recommended threads
- vorafy.studio domain already exists erro...
My domain vorafy.studio is stuck/locked from a previously deleted project. I created a new project but can't add the domain — getting 'already exists' error. Pl...
- How can I disable client-side account re...
Hi everyone! I’m currently building a game backend using Appwrite, and I’d like to prevent users from creating new accounts directly through the client. My go...
- relationships bug or error idk
hey every one, am using am using appwrite on a project and ran into a problem where by created a relationship and two way to be specific and it is stuck on proc...