Deployment in docker: where does elixir look for shared libraries?

You’re doing something wrong and the problem is probably not a library resolution path, but the issue seems to be that the release is compiled on some other system than you run it on.

Do you have a 2-stage Dockerfile that builds the release and then runs it in a different image? i.e. one maybe is Alpine and the other is Debian?

Or are you building the release locally on a different system and then copying it to the Docker image?

Or maybe you are copying the _build directory from the parent system to the Docker image?

Somehow you end up with Erlang being compiled for a different system that it runs on.

I was assuming the same thing, as I moved from alpine to Debian.

To make sure, this is not the case, I tested it with the build image itself. The same error appears here when copying it to the target (same) container.

I build the image in an Debian container with elixir/erlang installed and copy everything to the runtime container (Debian slim without elixir/erlang):

FROM debian:bullseye-slim AS app

RUN \
    apt update && \
    apt install -y \
      openssl \
      libncursesw6 \
      libstdc++6 \
      libgcc-s1 \
      zlib1g \
      wget \
      bash \
      musl-dev && \
    ln -s /usr/lib/x86_64-linux-musl/libc.so /lib/libc.musl-x86_64.so.1 

WORKDIR /app

RUN chown nobody:nogroup /app

USER nobody:nogroup
COPY --chown=nobody:nogroup _build/prod/rel/my_app ./

ENV HOME=/app
CMD ["bin/my_app", "start"]

Hi @christo-ph

It depends on the base image that you are using. Check out the following links as a good starting point for your elixir based docker file:

https://github.com/nickjj/docker-phoenix-example

HTH

I am using now the official elixir (slim) images, instead of compiling erlang/elixir directly. This works for the moment.

Still have to find the reason why my own pipeline fails here.

Thank you @hubertlepicki and @DonHubi