MIR-1430

Bring Your Own Image (converted to project)

Done public

phinze Opened Jul 17, 2026 Updated Aug 5, 2026

This issue has been converted to a project Bring Your Own Image

Companion issue for RFD-91.

Running a packaged, self-hostable app on Miren should be as easy as deploying your own code. Today, bringing an upstream image unchanged means a Dockerfile wrapper, a hand-built start command, and a chown shim: Miren drops the image's ENTRYPOINT, mounts disks root-owned, and defaults the port to 3000 instead of the image's EXPOSE.

The RFD proposes three changes so Miren inherits what the image declares and owns the platform side:

With no command, run the image's real ENTRYPOINT + CMD in exec form (not /bin/sh -c).
Default the service port to the image's EXPOSE.
Make a mounted disk writable by the run user by default (tracked separately in MIR-1428).

The shell-string command stays as the full-control escape hatch. The Chatto and Hermes deploys collapse to roughly "name the image."

Depends on MIR-1428. Lineage: MIR-468, MIR-621, MIR-929, RFD-79.