Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: LiteLLM container of latest dev (1.84.0-dev2) is broken for aarch64 (arm64) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26974•Fetched 2026-05-02 05:28:15
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
codgiciancodgician
Participants
blu3knightblu3knightcodgiciancodgician
Timeline (top)
labeled ×2renamed ×2subscribed ×2commented ×1

Error Message

litellm[456113]: {"msg":"exec container process /app/docker/prod_entrypoint.sh: Exec format error","level":"error","time":"2026-05-01T09:18:32.793516Z"} litellm[456113]: {"msg":"exec container process /app/docker/prod_entrypoint.sh: Exec format error","level":"error","time":"2026-05-01T09:18:32.793516Z"}

Code Example

litellm[456113]: {"msg":"exec container process `/app/docker/prod_entrypoint.sh`: Exec format error","level":"error","time":"2026-05-01T09:18:32.793516Z"}
podman[456099]: 2026-05-01 17:18:32.708270218 +0800 CST m=+0.825849171 image pull f7e98f4cd4127e71185912bbbd5d1117a6d1162d3fb34cff716ccb5fd4422098 ghcr.io/berriai/litellm:dev

---

litellm[456113]: {"msg":"exec container process `/app/docker/prod_entrypoint.sh`: Exec format error","level":"error","time":"2026-05-01T09:18:32.793516Z"}
podman[456099]: 2026-05-01 17:18:32.708270218 +0800 CST m=+0.825849171 image pull f7e98f4cd4127e71185912bbbd5d1117a6d1162d3fb34cff716ccb5fd4422098 ghcr.io/berriai/litellm:dev
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

Running the litellm:dev container on aarch64 Linux results in:

litellm[456113]: {"msg":"exec container process `/app/docker/prod_entrypoint.sh`: Exec format error","level":"error","time":"2026-05-01T09:18:32.793516Z"}
podman[456099]: 2026-05-01 17:18:32.708270218 +0800 CST m=+0.825849171 image pull f7e98f4cd4127e71185912bbbd5d1117a6d1162d3fb34cff716ccb5fd4422098 ghcr.io/berriai/litellm:dev

Looks like the wolfi-base used to build Aarch64 (arm64) container is having x86 binary.

Steps to Reproduce

  1. Run litellm:dev image on aarch64 Linux
  2. Observe that the container is unable to start

Relevant log output

litellm[456113]: {"msg":"exec container process `/app/docker/prod_entrypoint.sh`: Exec format error","level":"error","time":"2026-05-01T09:18:32.793516Z"}
podman[456099]: 2026-05-01 17:18:32.708270218 +0800 CST m=+0.825849171 image pull f7e98f4cd4127e71185912bbbd5d1117a6d1162d3fb34cff716ccb5fd4422098 ghcr.io/berriai/litellm:dev

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

1.84.0-dev2

Twitter / LinkedIn details

@codgician

extent analysis

TL;DR

Rebuild the litellm:dev container image using an aarch64-compatible base image to replace the x86 binary in wolfi-base.

Guidance

  • Verify that the wolfi-base image used in the build process is indeed the cause of the issue by checking its architecture compatibility with aarch64.
  • Check the Dockerfile or build configuration for the litellm:dev image to identify where the wolfi-base image is being used and update it to use an aarch64-compatible base image.
  • Consider using a multi-architecture base image that supports both x86 and aarch64 architectures to simplify the build process.
  • Test the updated image on an aarch64 Linux system to ensure it starts correctly.

Example

No code snippet is provided as the issue is related to the container build process and architecture compatibility.

Notes

The issue seems to be specific to the litellm:dev image and its build process, so the solution may not apply to other images or versions.

Recommendation

Apply workaround: Rebuild the litellm:dev container image using an aarch64-compatible base image to ensure compatibility with aarch64 Linux systems.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#chain error#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: LiteLLM container of latest dev (1.84.0-dev2) is broken for aarch64 (arm64) [1 comments, 2 participants]