Running a Phoenix application on a read-only filesystem

m_burg

I am trying to build a Phoenix application for Sandstorm. Sandstorm runs instances of applications in containers, grains, that all have a read-only filesystem. The only writeable directory is /var.

In order to prepare a grain a few scripts are run: setup.sh, build.sh, and launch.sh.

setup.sh is in charge of installing all the necessary dependencies in a VM to setup your development environment.

build.sh prepares the sources for your application.

launch.sh starts the actual grain.

In my build.sh I simply run MIX_ENV=prod mix compile to build my application. in launch.sh I start it with MIX_ENV=prod PORT=4000 mix phx.server.

When trying to start the application I get the following log output:

    Compiling 5 files (.ex)
    warning: redefining module HistorianWeb.PageController (current version loaded from _build/prod/lib/historian/ebin/Elixir.HistorianWeb.PageController.beam)
      lib/historian_web/controllers/page_controller.ex:1

    warning: redefining module HistorianWeb.Gettext (current version loaded from _build/prod/lib/historian/ebin/Elixir.HistorianWeb.Gettext.beam)
      lib/historian_web/gettext.ex:1

    warning: redefining module HistorianWeb.ErrorView (current version loaded from _build/prod/lib/historian/ebin/Elixir.HistorianWeb.ErrorView.beam)
      lib/historian_web/views/error_view.ex:1

    warning: redefining module HistorianWeb.LayoutView (current version loaded from _build/prod/lib/historian/ebin/Elixir.HistorianWeb.LayoutView.beam)
      lib/historian_web/views/layout_view.ex:1

    warning: redefining module HistorianWeb.PageView (current version loaded from _build/prod/lib/historian/ebin/Elixir.HistorianWeb.PageView.beam)
      lib/historian_web/views/page_view.ex:1

    ** (File.Error) could not write to file "/opt/app/_build/prod/lib/historian/ebin/Elixir.HistorianWeb.PageView.beam": read-only file system
        (elixir) lib/file.ex:953: File.write!/3
        (mix) lib/mix/compilers/elixir.ex:560: anonymous fn/4 in Mix.Compilers.Elixir.write_manifest/5
        (elixir) lib/enum.ex:1925: Enum."-reduce/3-lists^foldl/2-0-"/3
        (mix) lib/mix/compilers/elixir.ex:555: Mix.Compilers.Elixir.write_manifest/5
        (mix) lib/mix/compilers/elixir.ex:198: Mix.Compilers.Elixir.compile_manifest/9
        (mix) lib/mix/task.ex:316: Mix.Task.run_task/3
        (mix) lib/mix/tasks/compile.all.ex:68: Mix.Tasks.Compile.All.run_compiler/2
        (mix) lib/mix/tasks/compile.all.ex:52: Mix.Tasks.Compile.All.do_compile/4

Why does it need to compile more code? The fact that all the modules that are being redefined have the word view in their name suggests to me that this has something to do with templates.

Is there a way to compile this extra code before running the application? Or have it recompile without trying to write to the filesystem?

I am using Phoenix 1.3.4, because there are no SQLite adapters for Ecto 3 at the moment.

6 comments

/phoenix #deployment #containers

0 1983 6

2018-12-19 07:48:29 UTC

Showing Posts 6 to 1

Show Best Posts
Show All (oldest first)
Show All (newest first)

m_burg

That was indeed the problem.

Post #6

chrismcg

Check you’ve changed the :my_app to your actual app name where @repos is defined in the example code.

Post #5

m_burg

Using Distillery I have been able to get my application to start.

Right now I am stuck on getting migrations to run, though. I have tried following the instructions from the documentation, but my database does not get migrated when I run bin/historian migrate. There are no errors, just this output to the log:

Starting dependencies..
Starting repos..
Success!

Post #4

m_burg

You use Distillery for that, right? I’ll try that.

Post #3

OvermindDL1

The issue is that it looks like it’s being launched via mix instead of a release. mix is designed for development purposes, so it will often recompile a lot of things on every launch, especially as it dynamically loads modules.

Releases on the other hand don’t, they are static, and if build_embedded is on then all modules get statically loaded regardless (no hickups on first-loading of modules), etc… You always want to use a release.

Post #2

ConnorRigby

Nerves Core Team

I don’t do much work with Phoenix, but i know it is possible to deploy Elixir/Phoenix apps to a RO filesystem. That is how we deploy Nerves devices. We compile and build the release on a regular development machine and deploy the erlang release (which can in itself include erts removing the need to install erlang on your production machine)

Post #1

— All posts loaded —