title: ELF Header or installation issue with bcrypt in Docker container
body: <p>Kind of a longshot, but has anyone had any problems using bcrypt in a linux container (specifically docker) and know of an automated workaround? I have the same issue as these two:</p>
  
  <p><a href="https://stackoverflow.com/questions/17914744/invalid-elf-header-with-node-bcrypt-on-awsbox">Invalid ELF header with node bcrypt on AWSBox</a></p>
  
  <p><a href="https://stackoverflow.com/questions/15809611/bcrypt-invalid-elf-header-when-running-node-app">bcrypt invalid elf header when running node app</a></p>
  
  <p><strong>My Dockerfile</strong></p>
  
  <pre><code># Pull base image
  FROM node:0.12
  
  # Expose port 8080
  EXPOSE 8080
  
  # Add current directory into path /data in image
  ADD . /data
  
  # Set working directory to /data
  WORKDIR /data
  
  # Install dependencies from package.json
  RUN npm install --production
  
  # Run index.js
  CMD ["npm", "start"]
  </code></pre>
  
  <p>I get the previously  mentioned invalid ELF header error if I have bcrypt already installed in my node_modules, but if I remove it (either just itself or all my packages), it isn't installed for some reason when I build the container. I have to manually enter the container after the build and install it inside. </p>
  
  <p>Is there an automated workaround?</p>
  
  <p>Or maybe, just, what would be a good alternative to bcrypt with a Node stack? </p>