We were unable to connect to the registry for this image.
project id:
af3a9477-0f60-4b89-bf4f-fa5ff16bc99b
Rails 7.2.1 app that is fairly barebones is having issues building. Locally, the app works fine. There is a Dockerfile present, however I'm not using it when developing locally. But it is the one that auto generates with rails.
Looks to me it got through almost all of the build steps, but ultimately failed and says:
Solution:Jump to solution
ultimately, i had to use a database_url within rails to get railway to be happy. once i did that, it all worked. it's possible i wasn't using a db port or some piece of it that was causing the connection via env vars to fail
20 Replies
Project ID:
af3a9477-0f60-4b89-bf4f-fa5ff16bc99bwhat service? i dont see anything failed
Believe its service id: fea98c3a-19b1-44cc-8e0d-57c0189aebce
that service does not exist within the given project
thank you
it looks to be a very missleading message, i think this is user error
do you have any other information about the issue?
Let me try something - I just tweaked some files and got a different output.
from our logs -
open executable: Permission denied
we get that when we try starting your container, dont know why the user facing error is mentioning a registryI was able to setup the railway cli, and do a deploy up and now I can clearly see the issue.
awsome
:thinkingverymuch: I'm still having issues getting my DB connected. It seems like everything is setup correctly. I'm also getting
despite this page working just fine: https://relisa-api-production.up.railway.app/up
please read this section - https://docs.railway.app/guides/healthchecks-and-restarts#configure-healthcheck-port
Thx.
As for the DB, I'm getting:
my db config in code:
and I've got those 4 things set in my env in railway. Am I missing something?
is your app is trying to connect to a socket, then it is most definitely not using those environment variables
I’m not sure why it’s even doing the socket, I’ve never had a rails app do that.
Okay socket must mean by env vars are bad. I’ll try to sort that out.
sounds good
Was able to get it all done, thanks @Brody !
awsome, what was the issue?
Solution
ultimately, i had to use a database_url within rails to get railway to be happy. once i did that, it all worked. it's possible i wasn't using a db port or some piece of it that was causing the connection via env vars to fail
sounds good