musl | Unofficial mirror of etalabs musl repository. Updated daily.

This boils down to the following: When I use the settings

First, the SQLALCHEMY_DATABASE_URI in database.py should match the user, password and database name suplied in Your docker-compose.yaml. Ensure that You are running docker-compose up with correct environ. In Your case, the environ for docker-compose up should be:

I ended up using this command in my Dockerfile which did the trick:

I had a similar problem with a Rails app that has dependency on Nokogiri running on an Alpine based container on my Macbook M1. Here is what I did:

1. Reading the Nokogiri documentation, I found out that aarch64-linux (the architecture used inside the Docker container) is actually supported, but it requires glibc >= 2.29.

2. I am far from being an expert but, as far as I know, Alpine distributions don't include glibc but musl. Fortunately, there are ways to run programs that need glibc in Alpine.

3. I personally followed the first option, that is, I installed gcompat. I just needed to add gcompat to the list of packages to install in my Dockerfile.

   RUN apk add --no-cache ... gcompat

4. After that change, things went smoothly and the Rails app started up with no issues.

Again, I am not an expert and the above might be inaccurate, but it did the magic for me. I hope it can help you too.

I know it's been a while since this was asked, and you might've found a solution, or moved on from Alpine to a different distro. But I ran into the same issue, and this was the first thing that popped up on my search. So, after spending a couple of hours and finding a solution, I think it's worthwhile to document it here.

The issue is (obviously) with numpy and pandas packages. I used pre-built wheels from the community repo and ran into the same issue as you. So, evidently, the build process itself is introducing the issue. Specifically, if you look, e.g., under numpy/core at the install location (/usr/lib/python3.9/site-packages), you'll find that all the C-extensions have .cpython-39-x86_64-linux-musl in their name. So, for instance, the module you're having trouble with, numpy.core._multiarray_umath, is named _multiarray_umath.cpython-39-x86_64-linux-musl.so, and not just _multiarray_umath.so. Dropping the .cpython-39-x86_64-linux-musl from those filenames fixed the issue (edit: see addendum for details).

The following line can be added to your Dockerfile after installing py3-pandas and py3-numpy to fix it:

You can detect which Linux Distribution is running by following this StackOverflow answer

Unfortunately there aren't so many alternatives to detect if you are running on MUSL or GLIBC

It looks like the executable is actually named x86_64-linux-gnu-gcc, see https://packages.debian.org/bullseye/arm64/gcc-x86-64-linux-gnu/filelist.

It seems to me that's a path issue.

When setting subpart_1/repo_2/ in your docker-compose build file, the build will be done in this repertory. Docker will see the following files:

You can downgrade your Python version. That should solve your problem; if not, use collections.abc.Mapping instead of the deprecated collections.Mapping.

Refer here: Link