Docker image for Erlang VM with minimal memory/disk usage

Questions / Help
1

Hi guys,

Is there any Docker image I can use to build the smallest Erlang VM in term of memory usage and disk space?

Currently, I’m shipping my containers based on Ubuntu 22.04 LTS. They are pretty large and consume +200MB of RAM during startup (not even under load).

My task in the next weeks is to deploy more containers, and I can’t afford wasting memory like that.

Disclaimer: newbie here. I know only basics Docker.

Many thanks

2

If I just start an Erlang shell it uses about 37 MB of memory (as shown by erlang:memory(total)) and then another 13 MB in caches and pre-allocated memory (docker stats shows 50 MB of memory usage). To get that value down a bit I can start erl like this:

docker run -it erlang:26 erl +S 1 +SDio 1 +P 1024 +Q 1024 -mode minimal

That brings the memory usage down to 11 MB with 9 MB in caches etc, but it puts some constraints on the system that you might not want.

To decrease the amount of diskspace used, you should go for a multistage docker build where you only copy over your release. Like what is done here: GitHub - erlang/docker-erlang-example: HowTo Erlang in Docker and specifically in this Dockerfile.

4 Likes
3

@garazdawi thanks a lot. Let me give it go

4

Jade Allen talks about it in this presentation Code as infrastructure in the BEAM ecosystem - Jade Allen | Code BEAM Europe 2023 :slight_smile:

2 Likes
5

@garazdawi Is this still the case, or has the problem already been solved?

I came across this after reading Elixir question:
Using Alpine and musl instead of GNU libc affect performance?

6

@garazdawi -mode minimal seems undocumented. Is there any available information on what it does?

2 Likes
7

If you read the last comment of that issue you can see that it had nothing to do with using musl and yes it has been fixed.

1 Like
8

Using -mode minimal disables some kernel services mostly related to distribution and timers. I thought it was documented by apparently not. It has minimal effect on memory usage, but it does shave a few KBs off as a couple of processes are not started.

1 Like
9

@garazdawi when trying to compress the modules in the lib directory (except the NIF ones), my release doesn’t boot anymore. Got this error:

({load_failed,[lists,logger_config,logger_filters,logger,kernel,heart,file_io_server,file_server,file,error_logger,erl_parse,erl_lint,erl_eval,code,proc_lib,code_server,application_master,application,error_handler,logger_simple_h,logger_server,gen_server,gen_event,gen,filename,ets,logger_backend,supervisor,application_controller]})

Any idea?
Should I set a special flag when running the release containing .ez modules?

How to create a release that boots directly rom .ez archives
10

We just did a similar exercise with an Elixir app. We used Burrito to create a single executable that contains erts and the beam files (Erlang/Elixir/the app). The Docker image size went from 200MB down to 20MB.

We did a 2 phase build.

  1. Create a standard Dockerfile that creates a executable and an Elixir (mix) release.
  2. A minimized Dockerfile that just takes the executable and libraries required and produces a small image.

You could probably use a rebar3 deployable tarball instead of Burrito and mix release.

1 Like
11

Thanks a lot @nhpip. We use rebar3 of course for our Erlang releases and everything is working perfectly. Our images aren’t that small (~80MiB because we ship a code + many NIFs), but it’s OK.

My issue is with the .ez modules per @garazdawi suggestion.

12

@garazdawi could you please help with the .ez issue? Thanks