Error build
ds-digital-23
PROOP

2 years ago

Logs does not show the reason of failed build.

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

29 Replies

2 years ago

Mind sending full build logs here anyway?

Use this tool to send it: https://bookmarklets.up.railway.app/log-downloader/


ds-digital-23
PROOP

2 years ago

I remove docker file and try using only fastapi. railway.json {

"$schema": "https://railway.app/railway.schema.json",

"build": {

"builder": "NIXPACKS"

},

"deploy": {

"startCommand": "uvicorn app.main:app --host 0.0.0.0 --port $PORT"

}

}

Attachments


2 years ago

Are those all the logs available?


ds-digital-23
PROOP

2 years ago

Yeah


2 years ago

It just... stops?


2 years ago

Hey all, we're looking into this right now. Will update soon


2 years ago

As an update - the reason your build is failing is because the build container is OOMing when building your image. We're able to reproduce and have found that the new runtime significantly reduces memory usage and addresses the OOM. However, we're still investigating some transient errors so don't have a definitive answer quite yet.

That said, could we try enabling the new runtime on this service @ds-digital-23? We can switch it on from our side and troubleshoot your service directly, if you are okay with that.


ds-digital-23
PROOP

2 years ago

I agree. However, I removed 2 large files (103MB each). These are two YOLO models. Could I add them back?


2 years ago

Before you add them back, want to try building with the V2 runtime enabled and see how that goes? if it continues to fail, to get you unblocked we can disable V2 builder. All of this is done in the service settings.

Since we're able to reproduce, we can continue working on a fix and let you know when to switch back.


ds-digital-23
PROOP

2 years ago

Ok


ds-digital-23
PROOP

2 years ago

Hey, I created another project and worked it! However https://enecad-api-production.up.railway.app/docs gets Application failed to respond.

Attachments


2 years ago

For that, please see this docs page -

https://docs.railway.app/guides/fixing-common-errors


2 years ago

Amazing. Also FYI to both, we patched the issue that was causing the failures. Definitely please let me know if you see it again.


ds-digital-23
PROOP

2 years ago

Hi! I get it. But now I got an error about ASGI. It’s not clear for me. Could you guys help me?


2 years ago

Please provide the full build or deployment logs -

https://bookmarklets.up.railway.app/log-downloader/


ds-digital-23
PROOP

2 years ago

here

Attachments


2 years ago

Is this a fastapi app?


ds-digital-23
PROOP

2 years ago

That's right!


2 years ago

What's your start command?


ds-digital-23
PROOP

2 years ago

CMD ["sh", "-c", "uvicorn main:app --host 0.0.0.0 --port ${PORT:-8080}"] -> Inside the dockerfile


2 years ago

Do you have a start command set elsewhere like in your service settings?


ds-digital-23
PROOP

2 years ago

No


ds-digital-23
PROOP

2 years ago

I tried to set only one YOLO model, but got error.

Attachments


ds-digital-23
PROOP

2 years ago

Hi! Somebody? The same code runs well in other platform. Anyone helps?


2 years ago

Where are you storing these model files? and how big are they?


ds-digital-23
PROOP

2 years ago

Each one has 103MB (there are two YOLO models). They stored at "ia" folder.

Attachments


2 years ago

Meaning they are pushed into GitHub's LFS.

Railway will not pull files from LFS, you will need to find an alternative place to store those model files.


ds-digital-23
PROOP

2 years ago

Ah! Ok!


ds-digital-23
PROOP

2 years ago

Thanks!


Loading...