2 years ago
Hi,
I've started my first deployment and it failed after you registry http://us-west1.registry.rlwy.net/v2/ timed out.
I was wondering if it was a temporary issue.
Thanks.
ⓘ Deployment information is only viewable by project members and Railway employees.
7 Replies
2 years ago
Can you tell me more about your service config? do you have the v2 builder enabled? do you have the private network enabled?But more importantly, please provide the entire build logs - https://bookmarklets.up.railway.app/log-downloader/
2 years ago
Hi,
My service is a typical Rust application. Unfortunately, the repo is private so I cannot share with you more details.
I do have the v2 builder enabled.
I didn't do anything related to private networks yet, so I guess I don't have any enabled.
You'll see in the attached logs, the finale error is:
error pushing image: failed to push to destination us-west1.registry.rlwy.net/9e645685-ea25-41a1-8127-7d0528203174:6a41f65e-d5e7-4f37-97ff-7a70ef080c4b: Get "https://us-west1.registry.rlwy.net/v2/";: dial tcp [fd12::10]:443: connect: network is unreachable; Get "http://us-west1.registry.rlwy.net/v2/";: dial tcp [fd12::10]:80: connect: network is unreachable
This happens after many retries to connect to the registry.
Attachments
Status changed to Solved Railway • over 1 year ago
2 years ago
Could you try issuing a redeploy? This looks like it may be something on our end
2 years ago
Five has told me that this happens when you don't have private networking enabled.
2 years ago
It seems that enabling private networking worked!
Is this a temporary workaround or is this a requirement to be able to deploy with the v2 builder?
I'm asking because it's not obvious from my perspective.
Thanks for the quick reply and help!
2 years ago
For right now it is a requirement, once the v2 builder releases to GA it won't matter if you have private networking enabled or disabled.
