silverdr
Running Phx application inside docker container, I get regularly attacked by an EPMD zombie. While I am generally aware of
https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/
for example, my understanding is that this still applies to misbehaving processes. OTOH I wouldn’t expect part of the core Erlang stuff to misbehave so maybe I am simply unaware of something that I should / should not do when running Phx (or generally Elixir/Erlang stuff) inside a container? Any clues?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
Are you using EPMD for something? I think it is possible to start erlang runtime without using EPMD in newer versions.
silverdr
Currently no. It’s still single-host, single-node environment. Not starting
epmdat all if possible would help, although I’d prefer to understand the problem firstD4no0
EPMD is not started as a child process of erlang node, instead the mode of working is that it gets started with the runtime if it was not already started and the process is responsible for finding and marking all the active nodes on the host. I can confirm that this is true even for more exotic platforms such as android, it is most probably something that stuck historically.
I can’t confirm for sure but I remember reading about erlang deciding to ditch epmd in favor of another discovery system.
josevalim
In a release, you can set RELEASE_DISTRIBUTION=none and I think it won’t start EPMD.
silverdr
I read more erlang docs about EPMD and since i take it is run daemonised then most probably the
daemonised process scenario described (on nginx example) in the previously linked article kicks-in. Now.. how do I start a releases based Phx application so that the runtime doesn’t spawn this daemon?
silverdr
Hehe.. race condition
I’ll examine the suggestion, tnx
silverdr
I confirmed yesterday – passing
RELEASE_DISTRIBUTION=noneto the container prevents said zombie from surfacing. In the longer run a proper solution needs to be devised though. Probably something along the “phusion” base docker image lines. Thanks for all answerssilverdr
Yeah, especially that doing the workaround with
prevents connecting remote shell to it