Can't get past initialization, stuck at snapshot object not found
mannyyang
HOBBYOP

2 years ago

The title pretty much describes the issue. it gets stuck on the initialization phase and throws the error "object not found". I'm building from a dockerfile and for some reason it can't pick up that it's using a dockerfile either.

29 Replies

mannyyang
HOBBYOP

2 years ago

it works when i deploy to a previous commit but reverting to those changes still don't work


2 years ago

Can you try to duplicate your service?


mannyyang
HOBBYOP

2 years ago

yeah tried that as well, failed on the same step


2 years ago

Then this would be an issue with your GitHub repo somehow.

What is the size of the repo?


mannyyang
HOBBYOP

2 years ago

233 MBs in a zip

Attachments


2 years ago

Are you sure you are reverting to the correct commit, you need to revert to the expose port commit.


mannyyang
HOBBYOP

2 years ago

i'm reverting to the one that seems to be working

Attachments


2 years ago

please revert to the expose port commit.


mannyyang
HOBBYOP

2 years ago

mind explaining what this resolves? i would have to push new changes anyways no?


mannyyang
HOBBYOP

2 years ago

anyways, i rolled back to that commit. it built successfully, but pushing any variable updates throws the same error


mannyyang
HOBBYOP

2 years ago

if it's easier for you, i don't mind giving you read access to the repo


2 years ago

I think you are misunderstanding, please revert the GitHub commit, not the Railway deploy.

But yes read access would be good - brody192


mannyyang
HOBBYOP

2 years ago

ah sorry, I duplicated the project and set the commit to the one you asked: https://railway.app/project/f15fcaf7-8b92-4934-b4ae-d005e121cec4/service/5cadb0ef-8ad0-45dd-9bd8-0b8a4b62fd7d

still no luck though


mannyyang
HOBBYOP

2 years ago

the project folder in the repo is very simple though, it's only a dockerfile

Attachments


2 years ago

How is it 233MB?


mannyyang
HOBBYOP

2 years ago

the whole repo contains files for other projects, basically a monorepo


mannyyang
HOBBYOP

2 years ago

however, the other projects work but for some reason this specific project is failing


2 years ago

I am able to build with repo just fine with the root dir set to /flowise-docker

Can you try switching to the V2 runtime?


mannyyang
HOBBYOP

2 years ago

I have that set as well and now trying the v2 runtime

Attachments


mannyyang
HOBBYOP

2 years ago

no luck

Attachments


mannyyang
HOBBYOP

2 years ago

what's weird is that railway thinks it's still using a nix build when there's a docker file in there

Attachments


2 years ago

Purely a UI bug, I will not raise this to the applicable person.


mannyyang
HOBBYOP

2 years ago

got it, but yeah can't seem to get past the initialization step regardless


2 years ago

So what's with the working deploy from 2 mins ago? rollback?


mannyyang
HOBBYOP

2 years ago

that's correct


mannyyang
HOBBYOP

2 years ago

but yeah tried all sorts of different config updates and reverts in the past day, starting to pull my hair out on this :(. not really sure what change broke it


2 years ago

I've escalated this.


mannyyang
HOBBYOP

2 years ago

thank you


2 years ago

You've removed me from the repo, I'd need access to debug this efficiently.


Loading...