CODEWITHSUNDEEP
ruby-on-railssshgoogle-cloud-platformgoogle-cloud-run
Vishal Vijay
Vishal Vijay

Reputation: 2528

Access rails console of an app deployed in Google Cloud Run

We deployed a rails app in Google Cloud Run using their managed platform. The app is working fine and it is able to serve requests.

Now we want to get access to the rails console of the deployed app. Can anyone suggest a way to achieve this?

I'm aware that currently, Cloud Run supports only HTTP requests. If no other way is possible I'll have to consider something like rails web console

Upvotes: 3

Views: 1409

Answers (2)

Diogo Queiroz
Diogo Queiroz

Reputation: 11

Conventionally, as DazWilkin pointed out, it's not possible.

However, there is a workaround.

https://github.com/rails/web-console

This allows you to access the console via a browser section. Please note that this poses a significant security risk, be aware.

Upvotes: 0

DazWilkin
DazWilkin

Reputation: 40071

I think you cannot.

I'm familiar with Cloud Run but I'm not familiar with rails.

I assume you'd need to be able to shell into a container in order to be able to run IRB. Generally, you'd do this by asking the runtime (Docker Engine, Kubernetes, Cloud Run) to connect you to the container so that you could do this.

Cloud Run does not (appear) to permit this. I think it's a potentially useful feature request for the service. For those containers that contain shells, this would be the equivalent of GCE's gcloud compute ssh.

Importantly, your app may be serviced by multiple, load-balanced containers and so you'd want to be able to console into any of these.

However, you may wish to consider alternatives mechanisms for managing your app: monitoring, logging, trace etc. These mechanisms should provide you with sufficient insight into your app's state. Errant container instances should be terminated.

This follows the concept of "pets vs. cattle" whereby, instead of nurturing individual containers (is one failing?), you nurture the containers holistically (is the service comprising many containers failing?)

For completeness, if you think that there's an issue with a container image that you're unable to resolve through other means, you could run the image elsewhere (e.g. locally) where you can use IRB. Since the same container image will behave consistently wherever it's run, you should be able to observe the issue using IRB locally too.

Upvotes: 4

Related Questions