The selected runtime: UNSPECIFIED is not supported in this region: us-west2

arod1967HOBBY

4 months ago

The selected runtime: UNSPECIFIED is not supported in this region: us-west2. You can update the runtime in your service settings.

I have a app/rest and I need to update, but the platform change the region from us-west1 to us-west2, and don't deploy.

What I can do?

6 Replies

brodyEMPLOYEE

4 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody • 4 months ago

brodyEMPLOYEE

4 months ago

Switch to the V2 runtime in the service settings.

grantbirkiHOBBY

4 months ago

@arod1967, simply switching to V2 runtime in the service settings will allow your builds/deploys to pass at the expense of massive cost increases (to my findings). You may not want to upgrade to V2 (at least yet). You can see all my finding around this (from today) in this GitHub issue -> https://github.com/railwayapp/cli/issues/581

grantbirkiHOBBY

4 months ago

These are just my anecdotal experiences though and it may not apply to everyone. I also don't work at railway so I'm no expert on the internals here. As Brody also pointed out in that issue, Legacy isn't a good runtime to be on anymore. I think the cost increases on V2 are kinda concerning though.

brodyEMPLOYEE

4 months ago

Grant, I understand your concern but please do not recommend people stay on the Legacy runtime.

As for why there may be increased usage on the V2 runtime, this is the first we have heard of it and the V2 runtime has been out for about a year now, so it's likely that the legacy runtime was simply under counting CPU usage for your specific workload, there would be no issue there.

Eventually everyone will be moved to metal with the V2 runtime regardless of the runtime or region settings.

grantbirkiHOBBY

4 months ago

As for why there may be increased usage on the V2 runtime, this is the first we have heard of it and the V2 runtime has been out for about a year now, so it's likely that the legacy runtime was simply under counting CPU usage for your specific workload, there would be no issue there

Is this something that can be investigated? I don't mind upgrading to V2 again if it allows railway to inspect my resource and determine the price increases if it helps the broader community of other folks looking to upgrade their runtime.

Eventually everyone will be moved to metal with the V2 runtime regardless of the runtime or region settings.

Do you have further documentation about what metal is? I read through the docs on the v2 runtime changes already but haven't found anything specific as to what metal is.