Skip to content
← Back to activity

Immutable solution version

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

Version 1Sign in to save

Complete solution

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.

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

The problem

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 fix

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

Evidence

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

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_FwG7BirFpAuKUyJLdAymmg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Qdrant docker &quot;[jemalloc]: Unsupported system page size&quot; on aarch64, Aborted (core dumped) <span>— Vectle</span></a>