StrongLoop, Node, and tools.
NOTE: these images are mostly a proof of concept. If you want to use
StrongLoop in Docker you probably want to look at
strongloop/node image can be used interactive or as the base for other
strongloop/node comes in the following flavours:
- strongloop/node:latest - latest node compiled from source + strongloop
- strongloop/node:iojs - latest iojs compiled from source + strongloop
Once you have Docker installed and the
docker command working, you can pull
the image from Docker Hub:
$ docker pull strongloop/node # .... pulling down image
Now you can spin up a temporary Linux environment with node and strongloop
$ docker run -it strongloop/node bash $ slc --version strongloop v3.1.0 (node v0.10.38) ├── email@example.com ├── firstname.lastname@example.org (5a43a57) ├── email@example.com (1c78f8d) ├── firstname.lastname@example.org (9579431) ├── email@example.com (aab3dbb) ├── firstname.lastname@example.org (b23e63f) ├─┬ email@example.com (cd3897a) │ └── firstname.lastname@example.org ├── email@example.com (b90e9cd) ├── firstname.lastname@example.org └── email@example.com strongloop@2fc58988f424:~$ exit exit
strongloop/node as the base for an image, simply specify it in your
FROM strongloop/node # You start off as the 'strongloop' user. # If a RUN command needs root, you can use sudo # In addition to standard Linux commands you also have access to node, npm, # and slc commands # It is common to copy your current ADD . /home/strongloop/app WORKDIR /home/strongloop/app RUN npm install ENV NODE_ENV production CMD [ "slc", "run", "." ]
The "Source Repository" link is not valid (404 on GitHub)
Why is sudo required? It seems strange that the app directory is owned by root.
I've added sudo to the image, will be available as soon as docker hub finishes the build.
Comments mention you can use sudo, but the sudo command is not installed in the image.