[Bug]: Unable to deploy with NIXPACKS_NODE_VERSION = "22"

[actraiser]

Error Message and Logs

First of all, after upgrading, in all projects i get the "The latest configuration has not been applied" popup. When i try to Redeploy or push a new release for my app, the installation will stall (these are the final lines). My App is deployed from Github.

2025-Jan-21 13:39:23.276589
#10 CACHED
2025-Jan-21 13:39:23.276589
2025-Jan-21 13:39:23.276589
#11 [stage-0  6/14] COPY . /app/.
2025-Jan-21 13:39:23.628619
#11 DONE 0.5s
2025-Jan-21 13:39:23.779465
#12 [stage-0  7/14] RUN --mount=type=cache,id=rk88s40-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 npm install -g corepack pm2
2025-Jan-21 13:39:23.817098
#12 0.188 npm warn config production Use `--omit=dev` instead.

..... NO MORE LOGS FROM THIS POINT AND DEPLOY RUNS FOREVER ....

before the upgrade, the app deployment would instead continue like this:

#10 [stage-0  5/14] RUN sudo apt-get update && sudo apt-get install -y --no-install-recommends curl wget
2025-Jan-21 11:35:30.187438
#10 CACHED
2025-Jan-21 11:35:30.187438
2025-Jan-21 11:35:30.187438
#11 [stage-0  6/14] COPY . /app/.
2025-Jan-21 11:35:30.530163
#11 DONE 0.5s
2025-Jan-21 11:35:30.681611
#12 [stage-0  7/14] RUN --mount=type=cache,id=rk88s40-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 npm install -g corepack pm2
2025-Jan-21 11:35:33.206173
#12 2.675 
2025-Jan-21 11:35:33.206173
#12 2.675 added 137 packages, and changed 1 package in 3s
2025-Jan-21 11:35:33.206173
#12 2.675

..... and so on until sucessful deployment....
 

I have no idea what to check. I tried downgrading to Beta 380 but since database schema changed, i can not access my projects then anymore. So I had to revert back to the latest 384...,

Greets
-act

Coolify Version

v4.0.0-beta.384

[actraiser]

after further investigation, this seems to be a problem with nixpacks. I had the following node version configured in nixpacks.toml for my app.

NIXPACKS_NODE_VERSION = "22"

This worked fine until upgrading to Coolify Beta 384. Downgrading my Node Version here to "20" will make the build process succeed again.

Can you let me know if something has changed regarding nixpacks integration between Beta 380 and Beta 384?

Greets
-act

[peaklabs-dev]

What are you deploying?
maybe it is because of this #4871 (comment)

[actraiser]

What are you deploying? maybe it is because of this #4871 (comment)

I deployed a nodejs app. nixpacks should build and spin up using node v22 to run the app. This worked before but now i must specify "Node 20" in the nixpacks.toml file for the build to succeed. Any Idea why is Node 22 not working anymore since Beta 384?

-act

[peaklabs-dev]

Maybe this is Nixpacks related. I will update Nixpacks to the latest version in the next update and then we can investigate further.

[peaklabs-dev]

The new version has just been released, could you please re-test and let me know if this is fixed?

[actraiser]

Unfortunately using v4.0.0-beta.386 did not fix the problem for me. The deployment does still not proceed from this point when using Node 22 in nixpacks.toml (defined as NIXPACKS_NODE_VERSION = "22" )

2025-Jan-22 11:22:16.767854
#17 [stage-0 12/19] RUN --mount=type=cache,id=rk88s40-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 npm install -g corepack pm2
2025-Jan-22 11:22:16.767854
#17 0.115 npm warn config production Use `--omit=dev` instead.

Reverting to NIXPACKS_NODE_VERSION = "20" lets the build pass again. Is there any log I should inspect to get more information what happens at this point during the build process?

-act

[peaklabs-dev]

Can you please copy and paste the debug log of the deployment.

Also, can you maybe give me a sample repo so I can better reproduce the problem. Because I tested it with our sample repo and I cannot reproduce the issue, so this issue is probably related to what you are deploying because for my deplyments node 22 works just fine.

[actraiser]

I will create a basic repo over the weekend that mimics the application and deployment and let you know. Thank you for your work!

-act