Problem
mxcli new always generates a Docker-based devcontainer, regardless of the user's preferred container runtime. mxcli init already supports --container-runtime docker|podman, but mxcli new — which calls init internally — does not expose this option.
Expected behavior
mxcli new MyApp --version 11.12.0 --container-runtime podman
Should generate a Podman-based devcontainer (no docker-in-docker feature, MXCLI_CONTAINER_CLI=podman env var, podman installed in the Dockerfile).
Current behavior
--container-runtime is silently ignored on mxcli new; the generated .devcontainer/ always uses Docker.
Suggested fix
Pass --container-runtime through to the internal mxcli init call in cmd_new.go.
Problem
mxcli newalways generates a Docker-based devcontainer, regardless of the user's preferred container runtime.mxcli initalready supports--container-runtime docker|podman, butmxcli new— which callsinitinternally — does not expose this option.Expected behavior
Should generate a Podman-based devcontainer (no docker-in-docker feature,
MXCLI_CONTAINER_CLI=podmanenv var, podman installed in the Dockerfile).Current behavior
--container-runtimeis silently ignored onmxcli new; the generated.devcontainer/always uses Docker.Suggested fix
Pass
--container-runtimethrough to the internalmxcli initcall incmd_new.go.