> For the complete documentation index, see [llms.txt](https://docs.farmstack.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.farmstack.co/operation-guides/dockerization/dockerization-nodejs.md).

# NodeJS

## Overview

This tutorial will describe how to convert your NodeJS application to docker application for compatibility with FarmStack connector.

## Dockerization Process

Create a new file named `Dockerfile` in the application folder and open in your favorite text editor.

```
touch Dockerfile
```

Copy this code into the `Dockerfile`

First we are going to define the image we are going to use. Here we are using latest alpine image of node to keep the size of NodeJS application small. You can use any image available in the [Node's Dockerhub](https://hub.docker.com/_/node).

```bash
FROM node:alpine
```

Next we will create a directory to copy all our application code inside the image.

```bash
# Create app directory
WORKDIR /app
```

Since we are using node image, `node` and `npm` are already installed in this image. We just need to copy our `package.json` and `package-lock.json` files.

```bash
# Copy package.json and package-lock.json files to image
COPY package*.json ./

RUN npm install
```

Here, we copy `package.json` files before copying complete project. This is done to take advantage of Docker layers caching and only install dependencies if the files have changed. You can find more information about this [here](http://bitjudo.com/blog/2014/03/13/building-efficient-dockerfiles-node-dot-js/).

Now we will copy your app's source code to docker image.

```bash
# Copy app's source code
COPY . .
```

Our `sample-nodejs` app binds to port `8081` so we will map this port to docker `daemon` by using `EXPOSE` command. If your app uses any other port, kindly change it

```bash
EXPOSE 8081
```

In this last step, define the command to start your application. Our sample application starts with`npm start` command. You can also use a shell script file here which executes to start your server.

```bash
ENTRYPOINT ["npm","start"]
```

This should be your final `Dockerfile`

{% code title="Dockerfile" %}

```yaml
FROM node:alpine
# Create app directory
WORKDIR /app

# Copy package.json and package-lock.json files to image
ADD package*.json ./

RUN npm install

# Copy app's source code
COPY . .

EXPOSE 8081
ENTRYPOINT [ "npm", "start" ]
```

{% endcode %}

You can find the final `Dockerfile` [here](https://github.com/digitalgreenorg/farmstack-open/blob/main/tools/dockerfiles/NodeJS.Dockerfile).

### .dockerignore file

Create a `.dockerignore` file in the same directory as your `Dockerfile`. Add the following lines to the file:

{% code title=".dockerignore" %}

```bash
node_modules
npm-debug.log
.npm
```

{% endcode %}

## Next Steps

{% content-ref url="/pages/-MfdY-WXSKTGsF45YPVa" %}
[Install a dockerized application with connector](/operation-guides/install-a-nodejs-application-with-connector.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.farmstack.co/operation-guides/dockerization/dockerization-nodejs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.