mxcli docker run re-downloads MxBuild on Windows even when Linux binary already exists

[engalar]

Problem

On Windows host with Docker (WSL2), mxcli docker run re-downloads MxBuild every time, even when the Linux binary is already installed at ~/.mxcli/mxbuild/{version}/modeler/mxbuild.

Root cause

mxcli's setup check likely looks for mxbuild.exe (Windows convention) to determine if MxBuild is installed. But mxcli docker run needs the Linux binary (mxbuild without .exe), which was already extracted successfully. Since mxbuild.exe doesn't exist, mxcli assumes MxBuild is missing and re-downloads the 394 MB tarball.

Reproduction

# Windows 11, Git Bash
./mxcli setup mxbuild -p CarrefourAgent.mpr
# Downloads and extracts Linux mxbuild successfully

ls ~/.mxcli/mxbuild/11.6.4/modeler/mxbuild
# EXISTS - Linux ELF binary (76 KB)

ls ~/.mxcli/mxbuild/11.6.4/modeler/mxbuild.exe
# DOES NOT EXIST

./mxcli docker run -p CarrefourAgent.mpr --wait
# "Downloading MxBuild 11.6.4 for amd64..." ← downloads again!

Expected behavior

mxcli docker run should check for the Linux binary mxbuild (not mxbuild.exe) when preparing a Docker build, since Docker runs Linux containers.

Environment

• mxcli: 0.1.0
• OS: Windows 11 Pro (Git Bash)
• Docker: WSL2 backend
• Mendix: 11.6.4
• MxBuild tarball: ~394 MB (re-downloaded unnecessarily)

---

Copied from engalar#45

[github-actions]

Issue Triage

Summary:
On Windows with Docker (WSL2), mxcli docker run unnecessarily re‑downloads the MxBuild tarball because it checks for the Windows‑named mxbuild.exe instead of the Linux binary that was already installed.

Checklist (bug report)

Required info	Present?	Details
mxcli version	✅	0.1.0
Mendix version	✅	11.6.4
Scenario (what the user was trying to do)	✅	Ran mxcli docker run after a successful mxcli setup mxbuild
Expected output	✅	Should reuse the existing Linux mxbuild binary and not re‑download
Experienced output	✅	Shows “Downloading MxBuild 11.6.4 for amd64…” and re‑downloads the tarball
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:
To help us diagnose the issue, could you please run mxcli diag --bundle (or at least share the relevant session log) and attach the output to the issue? This will give us insight into the environment and the exact checks mxcli is performing.

Thanks for the clear report! Once we have the diagnostic bundle, we’ll be able to investigate further.

---

Automated triage via OpenRouter — workflow source