I am testing a docker deploy in a preview using the blueprint created preview environment with a Dockerfile for my service. The dockerfile is building and I can see it is always current after I push a change to my PR. Debug logging using echo from the Dockerfile or npm run command gives me confidence that it is always current.
However, I was having a problem where the server deploys but gets a runtime error at startup (I am playing with secret files and such). I tried using the Shell to connect and look at the files but the shell takes me to some instance that is not the current deployment. The times on the files and the content of the files have not changed for over an hour as I am testing deploys.
I could understand if the shell only works if render detects a green deploy… but I don’t like that it is taking me to an outdated filesystem / instance and no warning or indication it was outdated.
Is this a bug or is this just the way render shell works?
Once the deploy went green the shell now takes me to the actual current deployment.