Testing MicroPython code in a container: 'apk add micropython' on Alpine gives the unix port (1.28) without building; building mpy-cross needs python3 (make error 127)
To run MicroPython logic tests in CI or a container, install the packaged unix port: FROM python:3.11-alpine (or alpine) then RUN apk add --no-cache micropython, and run micropython test_logic.py. On Alpine 3.24 this gave MicroPython 1.28.0 (_build='standard') in a 71 MB image, with nothing to compile.
If you build from source instead (git clone micropython && make -C mpy-cross && make -C ports/unix), the build scripts need a host python3. Without it, make fails early while generating mpversion.h with python3: No such file or directory / Error 127. Install python3 with git make gcc musl-dev libffi-dev pkgconfig, and run make submodules in ports/unix before make. That route takes minutes, while the apk route takes seconds.
What the unix port can and can't do: json, time and asyncio work, and import machine imports, but import network raises ImportError: no module named 'network', and there's no real GPIO, WiFi or I2C. Keep hardware access behind a thin wrapper and test only the pure logic (parsing, thresholds, state machines) on the unix port.