Hi,
it’s been 2 days since we are experiencing this issue, we are not able to deploy an app that worked fine since 2 days ago.
I saw that could be an issue with allocated ram during the build phase, but I’m not able to change it.
Hello @Nextools ,
I asked the team to check your problem,
I’ll get back to you with more information soon.
Regards,
Charles-Edouard
Thank you! I started having the same issue on a self managed cluster. Before was working normally. It stays like that for 40 mins and then fails.
hello @Nextools ,
we checked your builder and we don’t see any resource problem
When comparing the failing build with some older builds, the difference is here
We can see the line 274 and 278:
Built in xxx seconds
And then on the left the timeout starts.
We don’t see any errors related to this.
Can you check in your dockerfile what is the next action?
Can you try to do the build on your machine to check if there is a difference?
Regards,
Charles-Edouard
Well, we did not change nothing. The build does work locally, also the docker build does work and the image has been created correctly.
We started experiencing this issue since 4 days now, and I see that randomly it happens also on our self-managed cluster.
It doesn’t happen for other applications we have deployed on the managed one, just for this one.
Could be an issue related to the resources of GCP? I checked the GCP quotas and everything is green, just “In-use regional external IPv4 addresses” is 7/8 used.
I also tried with different version of the docker image (FROM node:20-alpine, FROM node:22-alpine, etc), same problem.
Hello @Nextools,
we don’t have anything in the logs so it is hard to find the root cause.
I will escalate your problem to our tech expert to see if they can find more information on this topic.
I’ll get back to you if we find anything.
Regards,
Charles-Edouard
Hi @ce_gagnaire , thank you.
We are also checking from our side.
We tried the build locally and it works, tried the build of the docker container and it works.
Followup on that, seems that the issue was related to the updated Remix version in our app stack. Reverting to a previous version it worked and now is deployed. However no error and no other information were provided, this is why was strange. I think we can close it.
Thank you for your feedback.
I close this then.