api/Dockerfile

# base image
FROM pelias/baseimage
RUN useradd -ms /bin/bash pelias
USER pelias

# maintainer information
LABEL maintainer="pelias.team@gmail.com"

EXPOSE 3100

# Where the app is built and run inside the docker fs
ENV WORK=/home/pelias
WORKDIR ${WORK}

# copy package.json first to prevent npm install being rerun when only code changes
COPY ./package.json ${WORK}
RUN npm install

COPY . ${WORK}

# only allow containers to succeed if tests pass
RUN npm test

# start service
CMD [ "npm", "start" ]
Inherit from libpostal_baseimage 7 years ago			`# base image`
Update Dockerfile for libpostal service The Dockerfile no longer needs to be build on the libpostal_baseimage (which will probably go away soon) 7 years ago			`FROM pelias/baseimage`
Rewrite Dockerfile There were a couple problems with the current dockerfile: * It set the userid of the processes running in the container to 9999, without creating a user with that ID. This leads to confusion and an annoying message when you run an interactive bash session (the shell PS1 would display something like `I have no name!@1438586f786e:~$` * It tried to run `chown` on _all_ code files after running NPM install. This takes a really long time * It did not copy `package.json` and run `npm install` before copying other files. This means even a one line code change causes the image rebuild process to re-run `npm install`, which takes 30 seconds or so Now the image creates and uses a pelias user, sets permissions correctly from the start to avoid `chown`, and only runs `npm install` when it absolutely has to. 7 years ago			`RUN useradd -ms /bin/bash pelias`
			`USER pelias`
Use new maintainer label format 7 years ago
			`# maintainer information`
Dockerfile: Update to current Pelias contact email address Per https://github.com/pelias/pelias/tree/master/announcements/2018-01-02-pelias-update replace @mapzen.com email address in Dockerfile with the current Pelias contact email address. For example this will be visible from `docker inspect` with the other labels. 7 years ago			`LABEL maintainer="pelias.team@gmail.com"`
Preliminary Dockerfile 9 years ago
			`EXPOSE 3100`

			`# Where the app is built and run inside the docker fs`
Rewrite Dockerfile There were a couple problems with the current dockerfile: * It set the userid of the processes running in the container to 9999, without creating a user with that ID. This leads to confusion and an annoying message when you run an interactive bash session (the shell PS1 would display something like `I have no name!@1438586f786e:~$` * It tried to run `chown` on _all_ code files after running NPM install. This takes a really long time * It did not copy `package.json` and run `npm install` before copying other files. This means even a one line code change causes the image rebuild process to re-run `npm install`, which takes 30 seconds or so Now the image creates and uses a pelias user, sets permissions correctly from the start to avoid `chown`, and only runs `npm install` when it absolutely has to. 7 years ago			`ENV WORK=/home/pelias`
			`WORKDIR ${WORK}`
Preliminary Dockerfile 9 years ago
Rewrite Dockerfile There were a couple problems with the current dockerfile: * It set the userid of the processes running in the container to 9999, without creating a user with that ID. This leads to confusion and an annoying message when you run an interactive bash session (the shell PS1 would display something like `I have no name!@1438586f786e:~$` * It tried to run `chown` on _all_ code files after running NPM install. This takes a really long time * It did not copy `package.json` and run `npm install` before copying other files. This means even a one line code change causes the image rebuild process to re-run `npm install`, which takes 30 seconds or so Now the image creates and uses a pelias user, sets permissions correctly from the start to avoid `chown`, and only runs `npm install` when it absolutely has to. 7 years ago			`# copy package.json first to prevent npm install being rerun when only code changes`
			`COPY ./package.json ${WORK}`
			`RUN npm install`
Preliminary Dockerfile 9 years ago
Use COPY instead of ADD It has more predictable behavior: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#add-or-copy 7 years ago			`COPY . ${WORK}`
Preliminary Dockerfile 9 years ago
Rewrite Dockerfile There were a couple problems with the current dockerfile: * It set the userid of the processes running in the container to 9999, without creating a user with that ID. This leads to confusion and an annoying message when you run an interactive bash session (the shell PS1 would display something like `I have no name!@1438586f786e:~$` * It tried to run `chown` on _all_ code files after running NPM install. This takes a really long time * It did not copy `package.json` and run `npm install` before copying other files. This means even a one line code change causes the image rebuild process to re-run `npm install`, which takes 30 seconds or so Now the image creates and uses a pelias user, sets permissions correctly from the start to avoid `chown`, and only runs `npm install` when it absolutely has to. 7 years ago			`# only allow containers to succeed if tests pass`
			`RUN npm test`
Preliminary Dockerfile 9 years ago
Use best practices for CMD parameters See the section at https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/ 7 years ago			`# start service`
			`CMD [ "npm", "start" ]`