11 hours ago
Problem
Azure Container Registry (*.azurecr.io) isn't treated as a supported private registry in the UI. In the template editor it's not on the allowed-registries list, so the image field rejects any ACR path (e.g. .azurecr.io/:) as invalid regardless of format or credentials. In projects, the UI also blocks adding ACR images — they only work via the GraphQL API (serviceInstanceUpdate), not through the dashboard. "Generate Template
from Project" fails too, since it doesn't carry over private registry credentials.
What we'd like Railway to do
- Add *.azurecr.io to the supported private registries everywhere (service settings and the template editor), with credentials entered in the UI like the other private registries.
- Make "Generate Template from Project" carry over the source image.
Use case
Our production images live on Azure ACR. We want to deploy them via the dashboard and package our project as a reusable template — both are blocked today, forcing us to use the API or mirror images to another registry.
0 Threads mention this feature
0 Replies