Docker is not running.jcm says "Docker is not running (docker info did not answer)" and stops with exit
code 3. Start Docker Desktop (or sudo systemctl start docker) and run it again. "The docker command is not
installed" means it is not on your PATH.
Windows containers. Docker Desktop on Windows can run Windows or Linux containers; jcm needs Linux ones and
says "Switch to Linux containers" otherwise.
A port is in use.jcm run says a port is in use when 8080 (or the mail page's 8025) is taken; pass --port
and --mail-port, or stop what holds it.
Apple silicon. The tools image is built for your machine's own architecture (cli/build-image.sh builds
arm64 on an Apple silicon Mac); PostgreSQL, Mailpit and the JRE images are multi-architecture. Nothing runs
under emulation.
Windows line ends. The launchers keep their own line ends (cli/.gitattributes: jcm LF, jcm.ps1 and
jcm.cmd CRLF). Generated files are written with LF; the model's changelog checksums are taken on LF line ends,
so a checkout that turns them into CRLF (core.autocrlf=true) still passes checkJcmModel.
Windows paths. Run jcm in the project folder on a drive Docker Desktop shares (by default every local
drive under WSL 2). A path with spaces is fine. Containers jcm run starts never mount the project folder; the
jar is copied in, so their paths never depend on Windows' own.
Files owned by root on Linux. With rootful Docker the launcher passes your uid and gid and the image runs the
command as you; with rootless Docker the container's root is you already. A file owned by root (or by a
subordinate id under rootless Docker) was made by an older launcher: sudo chown -R $USER ..
Running from a subfolder. The project is the nearest folder at or above you with jcm-project.yml, else
settings.gradle (a multi-module build's top, not a module), else build.gradle; the command runs where you are.
When a Git repository holds the project further up (several projects in one repository), the launcher mounts the
repository's top, so jcm publish sees .git.
A path with a comma. The project is mounted with --mount type=bind,src=<path>, whose list is split at commas:
a project path containing a comma cannot be mounted. Move or rename the folder.
An old jcm-<name>-db volume. Before the database volume was named per checkout (jcm-<name>-<id>-db), it
was jcm-<name>-db; jcm run no longer uses that one. docker volume rm jcm-<name>-db once its data is not
wanted.
jcm new --dir outside the current folder is refused: the tools container sees only the folder jcm was
started in. Run jcm new from the folder that should hold the project.
Another JCM version. A project made with another JCM version than the launcher's says so at every command;
the image holds only its own version's artifacts. JCM_TOOLS_IMAGE=jcm-tools:<version> runs the matching one.
The first build is slow. It fills the jcm-cache volume. docker volume rm jcm-cache starts it over.
Where are the logs?jcm check: build/jcm-check/. jcm changelog: build/jcm-changelog.log. jcm run: .jcm/build.log for the build, and
docker compose -f .jcm/compose.yml logs app for the application.