Public | Automated Build

Last pushed: 2 months ago
Short Description
ember-cli v2.16.2 + node 8.7.0, bower 1.8.0, watchman 3.7.0
Full Description

Supported tags and respective Dockerfile links

This image is a fork of : danlynn/ember-cli (many thanks)

This image contains everything you need to have a working development environment for ember-cli. The container's working dir is /myapp so that you can setup a volume mapping your project dir to /myapp in the container.

ember-cli v2.16.2 + node 8.7.0 + npm 5.4.2 + bower 1.8.0 + watchman 4.7.0

How to use

Setup a project to use this container via docker-compose. docker-compose is part of the all-in-one docker-toolbox which is the easiest way to get up and running with docker.

  1. Create a docker-compose file with the same contents as the one in this project.

  2. Make sure that your docker-machine is already running:

     $ docker-machine start default
    

    Or, if you haven't created one yet:

     $ docker-machine create --driver virtualbox default
    
  3. Create an ember app in the current dir:

     $ docker-compose run --rm app ember init
    
  4. Start the ember server:

    $ docker-compose up
    

    OR

    $ docker-compose run --rm app ember server
    

    This launches the ember-cli server on port 4200 in the docker container. As you make changes to the ember webapp files, they will automagically be detected and the associated files will be recompiled and the browser will auto-reload showing the changes.

    Note that if you get an error something like

    app_1 | Error: A non-recoverable condition has triggered.  Watchman needs your help!
    app_1 | The triggering condition was at timestamp=1450119416: inotify-add-watch(/myapp/node_modules/ember-cli/node_modules/bower/node_modules/update-notifier/node_modules/latest-version/node_modules/package-json/node_modules/got/node_modules/duplexify/node_modules/readable-stream/doc) -> The user limit on the total number of inotify watches was reached; increase the fs.inotify.max_user_watches sysctl
    app_1 | All requests will continue to fail with this message until you resolve
    app_1 | the underlying problem.  You will find more information on fixing this at
    app_1 | https://facebook.github.io/watchman/docs/troubleshooting.html#poison-inotify-add-watch
    

    Then watchman is running out of resources trying to track all the files in a large ember app. To increase the fs.inotify.max_user_watches count to something that is more appropriate for an ember app, stop your docker-compose server by hitting ctrl-c (or docker-compose stop server if necessary) then execute the following command:

    $ docker run --rm --privileged --entrypoint sysctl opinioapp/ember-cli:2.16.2 -w fs.inotify.max_user_watches=524288
    

    Note that this will affect all containers that run on the current docker-machine from this point forward because fs.inotify.max_user_watches is a system-wide setting. This shouldn't be a big deal however, so go ahead and give it a try. Then start the docker-compose service again with

    $ docker-compose up
    
  5. Launch the ember webapp:

    You will need to first determine the IP of the docker container:

    $ docker-machine ip default
    -or-
    $ boot2docker ip
    
    192.168.59.103
    

    Next open that ip address in your browser on port 4200:

Command Usage

The ember, bower, and npm commands can be executed in the container to effect changes to your local project dir as follows. You basically put a "docker-compose run --rm app" in front of any of the 3 commands and pass the normal command options as usual.

Example:

$ docker-compose run --rm app npm install
$ docker-compose run --rm app bower install bootstrap
$ docker-compose run --rm app ember generate --pod model user
Docker Pull Command
Owner
opinioapp
Source Repository