zatae

zatae

Is this possible to deploy a Phoenix application to Google Cloud Run with MIX_ENV=dev ? For some reasons when I try deploy in dev mode, it just crash when the application starts.

Since Cloud Run is using gVisor, could this be possible that Phoenix is making some system calls that gVisor would consider as dangerous and just kill the process?

Showing Posts 1 to 8

timothy

timothy

We are running MIX_ENV=prod without any problems, not sure why mix_ENV=dev wouldn’t work. Maybe phoenix_live_reload causes this because it tries to access the filesystem (and requires inotify)? You should be able to find more information in the logs on Google Cloud.

zatae

zatae OP

After some digging :

"textPayload": "Uncaught signal: 10, pid=43, tid=43, fault_addr=0."

Based on this post, signal 10 is for sys_mprotect. So it seems that yes, Phoenix is making some calls in dev mode that trigger some security rules. If anyone has a workaround or more information about this, it would be really cool ! :slight_smile:

timothy

timothy

Which “execution environment” are you using? The second generation, which is still in preview though, might fix these system calls. This is what we are currently using.

According to the docs:

The second generation execution environment provides full Linux compatibility rather than system call emulation.

zatae

zatae OP

I tried but it also crash using gen2 (but thanks, I was not aware of this!). Do you think that hot reload / inotify can be part of the problem?

timothy

timothy

So I did some testing and it appears Google Cloud kills the application because the healthcheck fails. It test if the application is reachable on the given port. Since Phoenix runs on 127.0.0.1 in dev environment it isn’t available. So changing the ip configuration in config/dev.exs fixed the issue for me.

config :phoenix_cloud_run, PhoenixCloudRunWeb.Endpoint,
  # Binding to loopback ipv4 address prevents access from other machines.
  # Change to `ip: {0, 0, 0, 0}` to allow access from other machines.
- http: [ip: {127, 0, 0, 1}, port: 4000],
+ http: [ip: {0, 0, 0, 0}, port: 4000],
zatae

zatae OP

Even with the config/dev.ex update, for some reasons, this is not working for me. Do you use gen2 exec env? Anyway thanks for your help, I might have something else that is causing this crashes, I will investigate more in the next days.

timothy

timothy

I tested with both first-and second generation.

Did you change the port configuration on Cloud Run too? By default Cloud Run uses 8080 but Phoenix uses 4000 in dev environment.

zatae

zatae OP

That was it, totally forgot about that! Thank you very much for your help.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews