Skip to content

Latest commit

 

History

History
203 lines (133 loc) · 6.29 KB

containers.md

File metadata and controls

203 lines (133 loc) · 6.29 KB
Raw

Containers

This repository provides several Dockerfiles to enable building of OCI container images. This document has instructions for building and running the provided Dockerfiles in Docker and Podman. Refer to the Dockerfiles section to select the appropriate Dockerfile.

Dockerfiles

Pub Sub Service

  • Dockerfile.amd64 - Dockerfile used to build the Pub Sub Service for the x86-64 architecture.
  • Dockerfile.arm64 - Dockerfile used to build the Pub Sub Service for the aarch64 architecture.

Note: The default configuration files are cloned from .agemo/config, defined in the project's root.

Mosquitto MQTT Broker

  • Dockerfile.mosquitto.amd64 - Dockerfile used to build the Mosquitto MQTT Broker with the appropriate configuration for the x86-64 architecture.
  • Dockerfile.mosquitto.arm64 - Dockerfile used to build the Mosquitto MQTT Broker with the appropriate configuration for the aarch64 architecture.

Sample Applications

Note: The samples default configuration files are cloned from .agemo-samples/config, defined in the project's root.

Docker Containers

Prequisites

Install Docker

Running in Docker

To run the service in a Docker container:

  1. Run the following command in the project root directory to build the docker container from the Dockerfile:

    docker build -t <image_name> -f <Dockerfile> (optional: --build-arg=APP_NAME=<project name>) .

    For example, to build an image for the pub-sub-service project:

    docker build -t pub_sub_service -f Dockerfile.amd64 .

    Or to build an image for the chariott-publisher sample for aarch64:

    docker build -t chariott_publisher -f Dockerfile.samples.arm64 --build-arg=APP_NAME=chariott-publisher .

    Note: The build arg APP_NAME needs to be passed in for all sample applications to build the correct sample.

  2. Once the container has been built, start the container in interactive mode with the following command in the project root directory:

    docker run --name <container_name> --network=host -it --rm <image_name>

    For example, to run the pub-sub-service image built in step 1:

    docker run --name pub_sub_service --network=host -it --rm pub_sub_service

    Note: A custom network is recommended when using a container for anything but testing.

  3. To detach from the container, enter:

    Ctrl + p, Ctrl + q

  4. To stop the container, enter:

    docker stop <container_name>

    For example, to stop the pub_sub_service container started in step 2:

    docker stop pub_sub_service

Running in Docker with overridden configuration

Follow the steps in Running in Docker to build the container.

  1. To run the container with overridden configuration, create your config file and set an environment variable called CONFIG_HOME to the path to the config file:

    export CONFIG_HOME={path to directory containing config file}

  2. Then run the container with the following command:

    docker run -v ${CONFIG_HOME}:/mnt/config --name <container_name> --network=host -it --rm <image_name>

    For example, to run the pub_sub_service image with overridden configuration:

    docker run -v ${CONFIG_HOME}:/mnt/config --name pub_sub_service --network=host -it --rm pub_sub_service

Podman Containers

Prequisites

Install Podman

Running in Podman

To run the service in a Podman container:

  1. Run the following command in the project root directory to build the podman container from the Dockerfile:

    podman build -t <image_name> -f <Dockerfile> .

    For example, to build an image for the pub-sub-service project:

    podman build -t pub_sub_service -f Dockerfile.amd64 .

    Or to build an image for the chariott-publisher sample for aarch64:

    podman build -t chariott_publisher -f Dockerfile.samples.arm64 --build-arg=APP_NAME=chariott-publisher .

    Note: The build arg APP_NAME needs to be passed in for all sample applications to build the correct sample.

  2. Once the container has been built, start the container with the following command in the project root directory:

    podman run --network=host <image_name>

    For example, to run the pub-sub-service image built in step 1:

    podman run --network=host pub_sub_service

    Note: A custom network is recommended when using a container for anything but testing.

  3. To stop the container, run:

    podman ps -f ancestor=<image_name> --format="{{.Names}}" | xargs podman stop

    For example, to stop the pub_sub_service container started in step 2:

    podman ps -f ancestor=localhost/pub_sub_service:latest --format="{{.Names}}" | xargs podman stop

Running in Podman with overridden configuration

Follow the steps in Running in Podman to build the container.

  1. To run the container with overridden configuration, create your config file and set an environment variable called CONFIG_HOME to the path to the config file:

    export CONFIG_HOME={path to directory containing config file}

  2. Then run the container with the following command:

    podman run --mount=type=bind,src=${CONFIG_HOME},dst=/mnt/config,ro=true --network=host <image_name>

    For example, to run the pub_sub_service image with overridden configuration:

    podman run --mount=type=bind,src=${CONFIG_HOME},dst=/mnt/config,ro=true --network=host pub_sub_service