I'm trying to get my Sails.js app up and running using the standard node image but the build is failing when it tries to npm install bcrypt.

> [email protected] install /myapp/node_modules/bcrypt
> node-gyp rebuild

gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: node-v0.10.33.tar.gz local checksum 822ba41f2d77b704ab63e244dfef7431b31893c19bfe3bf228c06b6aff063ed5 not match remote 75dc26c33144e6d0dc91cb0d68aaf0570ed0a7e4b0c35f3a7a726b500edd081e
gyp ERR! stack     at deref (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:299:20)
gyp ERR! stack     at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:340:13)
gyp ERR! stack     at IncomingMessage.emit (events.js:117:20)
gyp ERR! stack     at _stream_readable.js:943:16
gyp ERR! stack     at process._tickCallback (node.js:419:13)
gyp ERR! System Linux 3.16.1-tinycore64
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /pos/node_modules/bcrypt
gyp ERR! node -v v0.10.33
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok 

My Dockerfile looks like:

FROM node:0.10.33

#  copy the source files into the image
ADD . /myapp

# Define working directory.
WORKDIR /myapp

# Install node-gyp as global
RUN npm install -g node-gyp && \
    node-gyp clean && \
    npm cache clean

# Install project dependencies
RUN npm install

# Expose sails port (still in development mind you)
EXPOSE 1337

# Define default command.
CMD ["node app"]

I've also raised a question on this over at stackoverflow with some more details.

@proppy pointed out that we've got a new version out and need to update ;)

Hello,

As I have reported here:
GoogleCloudPlatform/nodejs-docker#22
and here:
dockerfile/nodejs-runtime#2

the local node_modules dir is copied over the correct one in the container. I'm thinking this might only be a problem when the .dockerignore file is not supported. This is the case on Google Managed VM's.
Could someone verifie it works as intended so we know it's only a problem for Managed VM's?

Thanks!

npm support a --production flag, but due to the limitation of ONBUILD, I'm not sure how we can give the user some control on that downstream.

To make the example work I needed to change

docker build -t my-nodejs-app
docker run -it --rm --name my-running-app my-nodejs-app

to

docker build -t my-nodejs-app .
docker run -p 8888:8888 -it --rm --name my-running-app my-nodejs-app

node 0.11 has been updated to v0.11.14: http://blog.nodejs.org/2014/09/24/node-v0-11-14-unstable/

I'd have sent a PR but I saw you have a bunch of nice automated scripts in place. Please let me know if I can help with a PR anyway.

I'm trying to find a development workflow for OS X/Vagrant/Docker/node.js. If I were developing on OS X, I would use something like node-supervisor to restart the process during development. When I run the same server in in a Docker Container, supervisor doesn't restart the process.

Is it possible to run a node.js Container on OS X with hot-reload?

First, thanks for building a node image! We would recommend you upgrade the npm version contained in the image from 1.4.28 to 2.0.0 or later.

when build an image using this Dockerfile, it failed to retrieved the key:

sudo gpg --keyserver pgp.mit.edu --recv-keys 7937DFD2AB06298B2293C3187D33FF9D0246406D
gpg: directory /home/user/.gnupg' created gpg: new configuration file/home/user/.gnupg/gpg.conf' created
gpg: WARNING: options in /home/user/.gnupg/gpg.conf' are not yet active during this run gpg: keyring/home/user/.gnupg/secring.gpg' created
gpg: keyring `/home/user/.gnupg/pubring.gpg' created
gpg: requesting key 0246406D from hkp server pgp.mit.edu
gpgkeys: key 7937DFD2AB06298B2293C3187D33FF9D0246406D can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

I almost sent a trivial PR with COPY npm-shrinkwrap.json /usr/src/app, but the obvious problem is this breaks for projects without a shrinkwrap JSON. I don't (yet?) know how to fix this, so just opening an issue.

and there are lots of others that do.