How to pull from private docker registry?
I don't want to use railway as build-machine, but only as 'cloud' for my service.
How I can use private docker image here?
14 Replies
Project ID:
855671b7-88eb-4afa-9a53-6b654c4ae8c9855671b7-88eb-4afa-9a53-6b654c4ae8c9
private images are not currently supported, it is on the roadmap though
Is there anywhere we can track progress on this feature?
doesnt look like there is anything official in https://feedback.railway.app/ but it will eventually be supported, can i ask whats wrong with using railway's builder? its not like they charge for it lol
In my case, the build needs a little bit of setup with build-time secrets. I have an existing CI job that does this, so it would be convenient to have Railway just grab the resulting image.
I agree that it would definitely be convenient if railway could grab that image, but at the same time would the same build be impossible to setup on railway?
I'm not sure, I'm trying to figure that out now. I would need a way to access secrets before building the image. Does Railway have any secrets management?
there's service variables that you can access during the build in your dockerfile
Those are plain variables though, and available as runtime environment variables, correct? I'd like these to not be accessible outside the build.
why can't the variables be available during runtime?
To limit exposure. They are not needed at runtime.
if you dont expose them, they wont be exposed 🙂
An exploited instance would be the primary concern (for me). A script that dumps environment variables would expose them all.
Could a script be executed on deployment (entry point) that clears the environment variables that should never be exposed or used within the app?