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?
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
New
Hello all. I have a question as to best practices for code organization when implementing a liveview with a lot of responsibilities.
Sup...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance











Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
timothy
We are running
MIX_ENV=prodwithout any problems, not sure whymix_ENV=devwouldn’t work. Maybephoenix_live_reloadcauses 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
After some digging :
"textPayload": "Uncaught signal: 10, pid=43, tid=43, fault_addr=0."Based on this post, signal
10is forsys_mprotect. So it seems that yes, Phoenix is making some calls indevmode that trigger some security rules. If anyone has a workaround or more information about this, it would be really cool !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:
zatae
I tried but it also crash using
gen2(but thanks, I was not aware of this!). Do you think that hot reload /inotifycan be part of the problem?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.1indevenvironment it isn’t available. So changing the ip configuration inconfig/dev.exsfixed the issue for me.zatae
Even with the
config/dev.exupdate, for some reasons, this is not working for me. Do you usegen2exec 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
I tested with both first-and second generation.
Did you change the port configuration on Cloud Run too? By default Cloud Run uses
8080but Phoenix uses4000indevenvironment.zatae
That was it, totally forgot about that! Thank you very much for your help.