fast oak
I deployed a service via docker image (https://docs.railway.app/develop/services#service-source). Now when I call railway up in my github actions (with the RAILWAY_TOKEN set to that service's token), it does not deploy the docker images but instead tries to build my project using nixpacks. How can I instruct Railway to download the latest docker image and deploy it?
hidden beaconBOT
static brookBOT
fast oak
16582eee-f963-4f76-a699-aa37b8edbec1
green hamlet
railway up is used to deploy your local project and has nothing to do with docker images
what docker image did you use
fast oak
then just use the latest tag
how would railway know when I release a new image?
and will it deploy it then?
green hamlet
they dont, you have to go and click redeploy in the 3 dot menu
fast oak
thats a shame. does the public API have anything that can help me automate this?
i think it does
green hamlet
yes it does, you would want to setup a github action to call their public graphql api
fast oak
then just use the latest tag
how about caching? Will the image be cached on the Railway builders and when I redeploy, the existing image will be used instead of pulling the latest image. Anything I can do to prevent that?
green hamlet
if you redeploy the same image, yes the layers do get cached, if you deploy an entirely new image, no cache
fast oak
if you redeploy the same image, yes the layers do get cached, if you deploy an e...
well ghcr.io/ignisda/ryot:latest is technically the same image, right? Atleast thats what is docker's default behavior.
is there a env variable that instructs railway to not use docker caching mechanism?
green hamlet
is there a env variable that instructs railway to not use docker caching mechani...
there is not
green hamlet
well `ghcr.io/ignisda/ryot:latest` is technically the same image, right? Atleast...
as v2.18.7, yes
for now since that is the latest tag
fast oak
as v2.18.7, yes
of what?
green hamlet
your image
fast oak
my latest image is tagged both v2.18.7 and latest.
green hamlet
correct
fast oak
my latest image is tagged both `v2.18.7` and `latest`.
now lets say I release v2.18.8 (and a latest to go along with it). How would railway know to not re-use the existing cache?
fast oak
there is not
there used to be one back when I used railway almost 1.5 years ago. I think it was DOCKER_CACHE=0.
green hamlet
interesting
fast oak
because it's a different image
thats not how docker works. if you already have a ghcr.io/ignisda/ryot:latest on your machine, it does not check for SHA, just assumes it is the latest (even though it is not and there exists a newer image on the registry).
green hamlet
bruh
fast oak
there used to be one back when I used railway almost 1.5 years ago. I think it w...
I also think it was added specifically for me since I was in a similar situation back then.
