seb5law
I am bound by company policy to use Windows for development (only WIndows admins present…) but the productive system schould run on a CentOS.
I tried deploying a simple Phoenix app (converting user input as markdown to html code) using distillery as described in the Using Distillery With Phoenix article but removing the Erlang ERTS by setting set include_erts: false in rel/config.exs and compiling Erlang from source on CentOS.
I tried running the app but nothing happens, when I run the app with the foreground command I get the following error that I don’t comprehend:
bin/markdownhtml foreground
{"init terminating in do_boot",{load_failed, [gen,ets,supervisor,proc_lib,lists,kernel,heart,gen_server,gen_event,file_io_server,file_server,filename,file,error_logger,erl_parse,erl_lint,erl_eval,code_server,code,application_master,application_controller,application,error_handler]}}
init terminating in do_boot ()
Crash dump is being written to: erl_crash.dump...done
Shutting down node cleanly..
Node is not running!
What should this error tell me except that something went wrong?
How else do you suggest should I deploy?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
bobbypriambodo
Most likely it is a compatibility issue. From Erlang crash dump man page:
Excluding ERTS often result in faulty behavior. For consistency I guess it’s probably best to always bundle it.
Now, since the host system (Windows) is different from the target (CentOS), you have four options:
Option 1 and 2 can be done on your host machine. Option 3 needs you to have an extra server for building releases, and that might not be feasible depending on your company. I don’t think option 4 is recommended though, but it’s possible. Be aware that all options requires your container/VM/machine to have Elixir installed.
seb5law
Thanks for the reply, I chose the docker variant, but run the entire application via a docker container based on msaraiva/elixir. The deployment process I used is almost the same as and derived from the one described in this article.