v0.1.9 -- Full Docker CLI Flag Compatibility

Full Docker CLI Flag Compatibility

Mocker now matches Docker's CLI flag-for-flag across 111 commands and subcommands.

Highlights

• run / create: ~50 new flags -- --attach, --cpu-shares, --gpus, --init, --memory, --privileged, --restart, --security-opt, --shm-size, --ulimit, and more
• build: ~25 BuildKit/Buildx flags -- --cache-from, --cache-to, --load, --push, --secret, --ssh, --sbom, --provenance
• compose: ~200+ flags across 34 subcommands (was 22, added 12 missing ones)
• Network / Volume / System: all missing flags added

New Commands

• mocker commit -- create image from container changes
• mocker container prune -- remove stopped containers
• mocker container export -- export container filesystem
• mocker image rm / image inspect / image prune -- full image subcommand group

New Compose Subcommands

• compose events -- receive real-time events from containers
• compose attach -- attach to a service container
• compose commit / export -- image and filesystem operations
• compose scale -- scale services
• compose stats -- resource usage statistics
• compose version / volumes / wait / watch / bridge / publish

Documentation

• CHANGELOG.md -- full version history from v0.1.0 to present
• COMMANDS.md -- comprehensive reference of all 111 commands with every flag
• What's New sections added to both English and Chinese READMEs

Full Changelog

v0.1.8...v0.1.9

v0.1.8

ci: fix homebrew-tap commit author and update runner to macos-26

v0.1.7

fix: support compose.yaml / compose.yml as default compose file names

* Initial plan

* fix: support compose.yml and compose.yaml as default compose file names

Co-authored-by: kmplngj <562965+kmplngj@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

v0.1.6

fix: resolve named volumes to host paths for compose

Apple's container CLI does not support named volumes (-v name:/path).
Convert named volumes to their host mountpoint directories so bind mounts
are used instead (e.g. pgdata -> ~/.mocker/volumes/project-pgdata/_data).

v0.1.5

fix: resolve relative build context paths against CWD

URL(fileURLWithPath:).standardized does not resolve relative paths
like ../crw-opencore. Explicitly resolve against the current working
directory so build contexts like 'build: ../service' work correctly
in docker-compose.yml.

v0.1.4

fix: always pass -f flag to container build to use correct Dockerfile

container build defaults to CWD/Dockerfile, not context-dir/Dockerfile.
When compose build context is in a different directory (e.g. ../crw-opencore),
the wrong Dockerfile was being used. Now always pass -f with the resolved
absolute path to the Dockerfile in the build context directory.

v0.1.3

fix: add compose kill subcommand and --timeout flag to compose down

- Add `mocker compose kill [service]` to force-stop containers
- Add `--timeout <seconds>` option to compose down (default: 10)
- Fixes compatibility with dev.sh which uses both features

v0.1.2

fix: compose up accepts service names, compose down accepts --remove-…

v0.1.1

ci: add release workflow — build binary and update homebrew formula

v0.1.0 — Initial Release

Mocker v0.1.0

Docker-compatible container CLI built on Apple's Containerization framework (macOS 26+).

What's included

• Full Docker CLI: run, ps, stop, rm, exec, logs, build, pull, push, images, tag, rmi, inspect, stats
• Docker Compose v2: compose up/down/ps/logs/restart with depends_on ordering
• Network & Volume: network and volume subcommands
• Port mapping: -p hostPort:containerPort via persistent userspace TCP proxy
• Real stats: CPU% and memory from VM process
• Build: mocker build with live streaming output

Requirements

• macOS 26+ (Apple Silicon only)
• Apple's container CLI installed (/usr/local/bin/container)