5 months ago
I used to get this error every now and then, but things were solved when I redeployed. Now I'm unable to make any new deployments due to that error. The error indicates that it's related to the image build, which has nothing to do with the project itself because I'm not using Docker in my project, and it has something to do with Railway itself. Maybe the image cache! Honestly, I don't know what this error is about; it's not the first time, but this time it's causing downtime, so please, someone look into it. Please consider that we're in production and there should not be any downtime. I've included all the resources about this error. This is the second time I've posted this issue because the first time it got deleted, which is weird! It's a critical issue, and I believe that I clarified this in the urgency level, which is set to high. I'm on a pro account, and supposedly I have a higher response time! The issue has persists for over 24 hours now, and yet no answers, and on top of that, my older post got deleted.
9 Replies
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
.
Status changed to Awaiting Railway Response Railway • 5 months ago
brody
Please do not open duplicate threads.
5 months ago
It's not a duplicate thread. I only opened this thread after the previous one was somehow deleted. Since you finally had the time to respond, why don't you respond to the technical issue instead? It's clearly related to your platform. The error is caused by the Docker image that Railway uses to deploy my project; it's not even handled by me, which means I don't have any access to debug it. I believe this issue should be handled by your side.
5 months ago
Hi Kareem, this looks like it could be an application level issue and not related to Railway.
Does your app build locally without issues? The error suggests that TS is not able to find the right types for the glob module. Is this defined in your package.json?
Since you mentioned it intermittently happens could you give this a shot just in case — you're using Nixpacks, could you please try setting the NO_CACHE to 1? You can follow our documentation on how to do this https://docs.railway.com/guides/build-configuration#disable-build-layer-caching
If that doesn't work, could you please try switching from Nixpacks to Railpack and see if the build succeeds
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
Yes, it's defined and locally running fine and building fine, no issues. The last commit before the crash worked fine. The commit that caused the crash was literally a one-line commit in which I uncommented. About the NO_CACHE thing, we tried to add it to the environment variable, but the issue persists. Just to clarify, we have no access to the mentioned Docker image, as it's generated by Railway itself, not by our side.
Status changed to Awaiting Railway Response Railway • 5 months ago
chandrika
Hi Kareem, this looks like it could be an application level issue and not related to Railway.Does your app build locally without issues? The error suggests that TS is not able to find the right types for the glob module. Is this defined in your package.json?Since you mentioned it intermittently happens could you give this a shot just in case — you're using Nixpacks, could you please try setting the NO_CACHE to 1? You can follow our documentation on how to do this https://docs.railway.com/guides/build-configuration#disable-build-layer-cachingIf that doesn't work, could you please try switching from Nixpacks to Railpack and see if the build succeeds
5 months ago
Still there?
5 months ago
Guys, please! Are you aware of the situation? We're currently in production, and we're unable to push any updates because all of the builds fail. You keep repeating it's an application-level issue, but it's clearly not an application-level issue because we're not the ones who made this Docker image, and we're definitely not the ones responsible for it or its breakage. This is a high-urgency ticket!
5 months ago
This is the part of error I'd focus on
"Entry point for implicit type library 'glob'"
You should be able to configure:
tsconfig.json
```json
{
"compilerOptions": {
"types": [
"node"
],
},
}
```
Adding "node" should provide necessary global type definitions.
lmk if this solves it!
Attachments
eksno
This is the part of error I'd focus on"Entry point for implicit type library 'glob'"You should be able to configure:tsconfig.json```json{ "compilerOptions": { "types": [ "node" ], }, }```Adding "node" should provide necessary global type definitions.lmk if this solves it!
5 months ago
Thank you so much for your response, but could you please explain why you think this might solve the problem? Just for clarification because I don't understand why. I'd really appreciate it.