Containerizing the KeystoneJS application

Follow these steps:

1. Clone the repository in your development space: 

$ git clone https://github.com/legorie/gcpcookbook.git

2. Navigate to the directory where the mysite application is stored:

$ cd gcpcookbook/Chapter01/mysite-gke  

3. With your favorite editor, create a filename .env in the mysite folder:

PORT=8080 
COOKIE_SECRET=<a very long string> 
MONGO_URI=mongodb://mongo/mysite 

A custom port of 8080 is used for the KeystoneJS application. This port will be mapped to port 80 later in the Kubernetes service configuration. Similarly, mongo will be the name of the load-balanced MongoDB service that will be created later.

4. The Dockerfile in the folder is used to create the application's Docker image. First, it pulls a Node.js image from the registry, then it copies the application code into the container, installs the dependencies, and starts the application. Navigate to /Chapter01/mysite-gke/Dockerfile:

# https://github.com/GoogleCloudPlatform/nodejs-getting-started/blob/master/optional-container-engine/Dockerfile 
# Dockerfile extending the generic Node image with application files for a 
# single application. 
FROM gcr.io/google_appengine/nodejs 
# Check to see if the version included in the base runtime satisfies 
# '>=0.12.7', if not then do an npm install of the latest available 
# version that satisfies it. 
RUN /usr/local/bin/install_node '>=0.12.7' 
COPY . /app/ 
# You have to specify "--unsafe-perm" with npm install 
# when running as root.  Failing to do this can cause 
# install to appear to succeed even if a preinstall 
# script fails, and may have other adverse consequences 
# as well. 
# This command will also cat the npm-debug.log file after the 
# build, if it exists. 
RUN npm install --unsafe-perm || \ 
  ((if [ -f npm-debug.log ]; then \ 
      cat npm-debug.log; \ 
    fi) && false) 
CMD npm start

5. The .dockerignore file contains the file paths which will not be included in the Docker container.
6. Build the Docker image:

$ docker build -t gcr.io/<Project ID>/mysite .  

7. You can list the created Docker image:

$ docker images

8. Push the created image to Google Container Registry so that our cluster can access this image:

$ gcloud docker --push gcr.io/<Project ID>/mysite