Dojot Deploy - Docker Compose

This deployment option is best suited to development and functional environments. For production environment we recommend to use Kubernetes.

Getting Started

This repository contains the necessary configuration files for quick deployment of the Dojot Platform using docker-compose.

Requirements

Docker Engine >= 19.03 (Installation here)
Docker Compose >= 1.28 (Installation here)

Note: All tests were performed with Docker CE on Ubuntu 18.04 and 20.04.

Usage

Before running this deployment it's necessary to define your domain name or IP in .env file, in the DOJOT_DOMAIN_NAME variable.

To start the containers, the following profiles are available:

basic (minimum services)
mongodb-pesistence
data-processing
cron-job
x509-certificates
front-end
lwm2m-iot-agent
device-management
api-gateway
user-management
data-processing-context
websocket-real-time
iot-agent-mqtt
iot-agent-http
import-export-configuration
influxdb-persistence
file-management
complete (all services)

Start the containers with the minimum services using the command below:

docker-compose --profile basic up --detach

Or start all services with below command:

docker-compose --profile complete up --detach

Note: To get completely ready, healthy :green_heart:, all services in this docker-compose take an average of at least 12 minutes.

For instructions on how to get it up and running, please check Installation Guide. Always change the admin user password to a suitable password and keep it safe.

Both are available in the Docker Official Site.

How to run dojot with HTTPS

Secure dojot with Let's Encrypt (recommended)

To get dojot running with https, at least for the purposes of this guide, you MUST ensure you have set up a static public IP address for your server and registered a domain for it. Then just follow the next steps.

Firstly, configure a temporary Nginx server that only runs on HTTP and gives the Certbot tool write access for the following endpoint: http:///.well-known/acme-challenge/{token}. This endpoint will be used to answer Let's Encrypt CA's challenge, which is part of the process of getting a certificate for your server.

To make the things easier, there is a docker-compose configuration file in letsencrypt-nginx/docker-compose-challenge.yml. But, before starting it, change the file letsencrypt-nginx/nginx-challenge.conf, replacing tag by your registered domain. Then spin up Nginx:

# Go to the repository letsencrypt-nginx
cd letsencrypt-nginx
# Start the Nginx container
sudo docker-compose --file docker-compose-challenge.yml up --detach

The next step is to run Certbot tool. Change the command bellow to use your email address and your domain, and just run it.

sudo docker container run -it --rm \
    -v /dojot/etc/letsencrypt:/etc/letsencrypt \
    -v /dojot/var/lib/letsencrypt:/var/lib/letsencrypt \
    -v /dojot/letsencrypt-site:/data/letsencrypt \
    -v /dojot/var/log/letsencrypt:/var/log/letsencrypt \
    certbot/certbot \
    certonly --webroot \
    --email <youremail@domain.com> --agree-tos --no-eff-email \
    --webroot-path=/data/letsencrypt \
    -d <your domain>

If everything ran successfully, stop the temporary Nginx server because it is no more necessary:

sudo docker-compose --file docker-compose-challenge.yml down

Now you have a certificate for your domain. The next step, is to configure a Nginx to receive the https requests and redirect the traffic to dojot's api gateway.

This Nginx service is specified in the docker-compose file letsencrypt-nginx/docker-compose-dojot-https.yml. It MUST run in the same network of other dojot's services. So before starting it, change the network in the configuration if necessary and replace the tag by the your registered domain in the files: letsencrypt-nginx/docker-compose-dojot-https.yml and letsencrypt-nginx/nginx-dojot-https.conf. Then spin up Nginx:

sudo docker-compose --file docker-compose-dojot-https.yml up --detach

Now, open up a browser and visit https://. You should see the dojot's graphical interface.

Periodically, you need to renew the certificate. The process is very simple, run a Certbot command and restart the Nginx. To automate it with a cron job, run:

# open crontab editor
sudo crontab -e

Place the following at the end of the file, then close and save it.

0 23 * * * docker container run --rm --name certbot \
    -v "/dojot/etc/letsencrypt:/etc/letsencrypt" \
    -v "/dojot/var/lib/letsencrypt:/var/lib/letsencrypt" \
    -v "/dojot/data/letsencrypt:/data/letsencrypt" \
    -v "/dojot/var/log/letsencrypt:/var/log/letsencrypt" \
    certbot/certbot renew --webroot -w /data/letsencrypt --quiet && docker restart https-nginx

The above command will run every night at 23:00, renewing the certificate and forcing Nginx to restart if the certificate is due for renewal.

Secure dojot with self-signed certificate

To get dojot running with https with self-signed certificate, the domain/ip must be accessible where dojot is running and inside the docker network.

As prerequisites this uses OpenSSL.

On Debian-based Linux distributions, you can install these prerequisites by running:

sudo apt install openssl

After installing the prerequisites if necessary, generate certificates

cd self-signed-certificate-nginx
openssl req -x509 -nodes -newkey rsa:2048 -days 365  \
  -keyout dojot-nginx-certificate.key -out dojot-nginx-certificate.crt -subj '/CN=*<server IP>*,*<server Name>*' \
  -addext 'subjectAltName=DNS:*<server Name>*,IP:*<server IP>*'

Example:
openssl req -x509 -nodes -newkey rsa:2048 -days 365  \
  -keyout dojot-nginx-certificate.key -out dojot-nginx-certificate.crt -subj '/CN=dojot_CPQD' \
  -addext 'subjectAltName=DNS:gcp-eun-doc,IP:10.233.48.15'

Now you have a certificate. The next step, is to configure a Nginx to receive the https requests and redirect the traffic to dojot's api gateway.

This Nginx service is specified in the docker-compose file self-signed-certificate-nginx/docker-compose-dojot-https-self-signed-certificate.yml. It MUST run in the same network of other dojot's services.

sudo docker-compose --file docker-compose-dojot-https-self-signed-certificate.yml up --detach

Open up a browser and visit https://.

You should see an error message telling the connection is not safe.

Now you need to click on the warning botton next to your IP address.

Then click in the option telling the certificate is not valid.

Enter in details tab and export the certificate adding extension ".crt" .

The next step, it is upload the certificate (that you exported) in your browser.

*Chrome*

Settings -> Privacy and Security -> Security -> Manage certificates -> Autorities -> Import

Choose the saved file (example: dojot_CPQD.crt)

Check all the options in the box and click OK

Reload the connection in the browser and now your connection is safe and the certificate is recognized by the browser.

*Firefox*
The certificate is recognized by the browser automatically

If you will use http-agent to send message with self-signed certificate, it is necessary configure the http-agent-cert-sidecar environment variable CERT_SC_CERTS_HOSTNAMES including the server IP and server name

Example:
CERT_SC_CERTS_HOSTNAMES: '["http-agent", "${DOJOT_DOMAIN_NAME:-localhost}", "<server IP>", "<server Name>"]'

Note: It is very important to include the quotes in the server IP and server name

Now, apply the changes running:

docker-compose --profile complete up -d

If you will use iotagent-mqtt to send message with self-signed certificate, it is necessary configure the iotagent-mqtt-cert-sidecar environment variable CERT_SC_CERTS_HOSTNAMES including the server IP and server name

Example:
CERT_SC_CERTS_HOSTNAMES: '["iotagent-mqtt", "${DOJOT_DOMAIN_NAME:-localhost}", "<server IP>", "<server Name>"]'