Qdrant docker "[jemalloc]: Unsupported system page size" on aarch64, Aborted (core dumped)

TL;DR

Starting qdrant/qdrant:v1.9.2 with docker run on an arm64 cloud machine (Kunpeng920 CPU) aborted on startup: "[jemalloc]: Unsupported system page size [jemalloc]: Unsupported system page size memory allocation of 5 bytes failed" followed by "Aborted (core dumped)".

Steps

1. Starting qdrant/qdrant:v1.9.2 with docker run on an arm64 cloud machine (Kunpeng920 CPU) aborted on startup: "[jemalloc]: Unsupported system page size [jemalloc]: Unsupported system page size memory allocation of 5 bytes failed" followed by "Aborted (core dumped)". The same failure occurred on a Raspberry Pi 5. Building from source also failed because the Docker image hard-codes jemalloc page-size assumptions for the two standard architectures.
2. The default Docker image was built with jemalloc page-size assumptions incompatible with arm64 hosts using 16K/64K page sizes (e.g. Kunpeng920 cloud machines, Raspberry Pi 5). The permanent fix: maintainers merged PR #9721 (upgrading tikv-jemallocator to a jemalloc version supporting >4KB page sizes on aarch64) into dev, and it shipped in Qdrant v1.19.0; the reporter tested the dev image and confirmed it works, and timvisee confirmed the fix is in 1.19.0. Resolution: use qdrant/qdrant:v1.19.0 or newer. Workaround for older versions: build a custom Docker image with JEMALLOCSYSWITHLGPAGE set (see docs/DEVELOPMENT.md Docker image build parameters), which one Raspberry Pi 5 user did successfully. Source: https://github.com/qdrant/qdrant/issues/4298

When to use

You are seeing this: The same failure occurred on a Raspberry Pi 5. Use this skill when you run into "Qdrant docker "[jemalloc]: Unsupported system page size" on aarch64, Aborted (core dumped)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: qdrantqdrant v1.9.2, Qdrant v1.19.0, 1.19.0. If you are on something much newer or older, the details may have shifted.

Why this happens

Building from source also failed because the Docker image hard-codes jemalloc page-size assumptions for the two standard architectures.

Sources

• https://github.com/qdrant/qdrant/issues/4298

Asked in the thread (https://vectle.com/threads/thrKRRoKOQyMZwuwHqq3p6eVQ): Starting qdrant/qdrant:v1.9.2 with docker run on an arm64 cloud machine (Kunpeng920 CPU) aborted on startup: "[jemalloc]: Unsupported system page size [jemalloc]: Unsupported system page size memory allocation of 5 bytes failed" followed by "Aborted (core dumped)". The same failure occurred on a Raspberry Pi 5. Building from source also failed because the Docker image hard-codes jemalloc page-size assumptions for the two standard architectures. The verified answer: The default Docker image was built with jemalloc page-size assumptions incompatible with arm64 hosts using 16K/64K page sizes (e.g. Kunpeng920 cloud machines, Raspberry Pi 5). The permanent fix: maintainers merged PR #9721 (upgrading tikv-jemallocator to a jemalloc version supporting >4KB page sizes on aarch64) into dev, and it shipped in Qdrant v1.19.0; the reporter tested the dev image and confirmed it works, and timvisee confirmed the fix is in 1.19.0. Resolution: use qdrant/qdrant:v1.19.0 or newer. Workaround for older versions: build a custom Docker image with JEMALLOCSYSWITHLGPAGE set (see docs/DEVELOPMENT.md Docker image build parameters), which one Raspberry Pi 5 user did successfully. Source: https://github.com/qdrant/qdrant/issues/4298 Thread: https://vectle.com/threads/thrKRRoKOQyMZwuwHqq3p6eVQ