I haven’t been able to update my app for a few days now. It keeps getting stuck on this line
“Saving registry.fly.io/[app name] cache”
Please help! I’m not sure what’s changed to make it get stuck here but even after 1.5 hours it was still on the same line
Hm… I don’t see that line in my own builds, although those are non-Depot…
Maybe try --depot=false or --recreate-builder?
Failing that, it would probably help to post more context (lines preceding the one that you quoted). The </> button in the toolbar can be used to get an area suitable for pasting code, outputs, etc.
The node install, npm install, and node modules installs seem to be fine besides some deprecated package warning (which have been there)
The issue comes on the Exporting step
- Running scripts
- No build scripts found
- Configuring default processes
- Skipping default web process (Procfile detected)
- Done (finished in 30.3s)
===> EXPORTING
Adding layer 'heroku/nodejs-engine:available_parallelism'
Adding layer 'heroku/nodejs-engine:dist'
Adding layer 'heroku/nodejs-engine:web_env'
Adding layer 'heroku/nodejs-npm-engine:npm_engine'
Adding layer 'heroku/nodejs-npm-install:npm_runtime_config'
Adding layer 'buildpacksio/lifecycle:launch.sbom'
Added 1/1 app layer(s)
Adding layer 'buildpacksio/lifecycle:launcher'
Adding layer 'buildpacksio/lifecycle:config'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
no default process type
Saving registry.fly.io/[app]:cache...
It doesn’t go past this point.
Was this with --depot=false?
no, I’ve never used that flag. I’ll try it out though
Same issue unfortunately even with --depot=false
Sorry to hear that you’re still having trouble, 
… People have generally been nudging users away from the buildpacks of late:
Also…
Consequently, if you are using a buildpack, then perhaps the next troubleshooting step is to switch to an explicit Dockerfile.
@rubys has an npx invocation that generates a credible starter one, if I understand correctly. (I don’t use Node myself, though.)
If you search the forum archives, you should see it come up several times—and then you can gauge whether it fits your particular context, etc.
Hope this helps a little!
I had the same issue. For some context, I have a hobby node.js project running an Express server which I stood up a few years ago with a heroku buildpack. I have to update an API token once a year for this project and get reacquainted with deploying on fly, and this year the deploy stalled on the same stage for me as it did for you
@mayailurus 's advice of switching to an explicit Dockerfile worked for me. I deleted my old, buildpack-based fly.toml file, then ran fly launch --no-deploy to generate a new fly.toml and Dockerfile (this opened a browser window for me and I had to enter a dummy name for the “new project” to be able to generate these build files, and then adjust the resulting files to use the actual name of my existing project).
From this point I had to make a couple small adjustments to my project so that the default settings that fly uses would expose my app (e.g. ports/addresses), so depending on how involved your project is this could be slightly more painful for you, but this ended up working for me. Best of luck, and thanks for the advice mayailurus
This worked for me too! Thanks @mayailurus and thank you for the instructions on how to generate a dockerfile, i didn’t need to make many changes to mine so it worked perfectly! It’s much faster to update too now which is a nice plus.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.