ember-cli

Mount your project directory at /myapp and the container hands you a full ember-cli environment: ember-cli 7.1.0, node, npm, bower, yarn, chrome, and watchman, with nothing installed on the host.

This is a Docker image built around ember-cli, and the whole point is that the development toolchain rides along inside it. The container sets its working directory to /myapp, so a volume mapped there keeps your project visible to whatever runs inside. The README pins the versions: ember-cli 7.1.0, node 24.18.0 or 26.5.0, npm 11.16.0 or 11.17.0, bower 1.8.8, yarn 1.22.22, chrome 150.0.7871.128, and watchman 4.9.0. The image is MIT licensed, and nothing on the host has to be installed to get that consistent Ember environment. That is the whole pitch: one pull, and the build tooling is just there.

A worked example walks through the Ember Octane Quick Start using docker-compose. It follows the instructions from the ember-cli docker-compose template, which is itself built around this image, so there is a reference setup to copy rather than something to assemble from memory. For anyone still learning Octane, the example doubles as a starting point for wiring a real project to the image with compose.

People who used the image before version 6.8.0 should expect one difference. The regular ember server command has been replaced with npm start plus the host flag set to 0.0.0.0, and existing usage and launch scripts need to move to the new form. The change is documented up front, which is exactly what you want from a breaking shift buried inside a toolchain image.

The README steers readers toward docker-compose as the easiest route and links a stub template repository configured to use this image. The fine detail of the optimized compose environment lives in that template's own README. Beyond the image, the example, and the version shift, the documentation keeps a fairly tight scope.

• Source 1 · Project repository
• Source 2 · README