Create a Docker-Compose App¶

In the Configuring Git section, you should have set up git with your auth token, meaning you can clone your Factory repositories from https://source.foundries.io/factories/<factory>/ and begin creating new Targets for your devices to update to.

Tip

To help illustrate the update process, you can compare the output of some commands like fioctl devices list (on host machine) and docker ps (on device) running before and after enabling an example app or demo. You can also check the Devices tab at https://app.foundries.io for the current target your device is running.

Example Apps¶

This default example shows how apps are enabled. You should read the contents of the shellhttpd folder to see how this application has been defined, or read the other examples to learn how you can define an app from scratch.

Clone your containers.git repo and enter it:
```
git clone https://source.foundries.io/factories/<factory>/containers.git
cd containers.git
```
We initialise your containers.git repository with a simple compose app example in shellhttpd.disabled/

Tip

Directory names ending with .disabled in containers.git are ignored by our CI system.
Enable the shellhttpd example app:
```
mv shellhttpd.disabled shellhttpd
```

Add, commit and push:

git add .
git commit -m "shellhttpd: enable shellhttpd app"
git push

Watch Your Build

When changes are made to containers.git in your Factory sources, a new Target is built by our CI system. Devices that are registered to your Factory will be able to see this Target and conditionally update to it, depending on their device configuration.

Device Configuration

Once the Target is built successfully, any devices that are registered to the Factory will begin updating to this new Target. The app shellhttpd that has been defined will be available for usage in this Target. This can be verified by running:

fioctl targets list

By default devices will run all applications that are defined in the containers.git repository and therefore available in the latest Target. This behavior can be changed by enabling only specific applications. Read Enabling/Disabling Apps to learn how.

This example describes how to create a docker-compose app for the Mosquitto MQTT Broker from scratch.

Clone your containers.git repo and enter it. Make sure to replace <factory> in the example with the name of your Factory:
```
git clone https://source.foundries.io/factories/<factory>/containers.git
cd containers.git
```
Create a directory named mosquitto and cd into it. This folder name defines the name of the container image that will be pulled on your device from hub.foundries.io:
```
mkdir mosquitto
cd mosquitto
```
Create a file named Dockerfile to describe your container, with the following contents:
```
FROM eclipse-mosquitto:latest
```
Create a file named docker-compose.yml to describe how you want this container to run, with the following contents. Make sure to replace <factory> in the example below with the name of your Factory:
```
version: "3.2"

services:
  mosquitto:
    restart: always
    image: hub.foundries.io/<factory>/mosquitto:latest
    ports:
      - "1883:1883"
```

Add, commit and push:

git add .
git commit -m "mosquitto: create mosquitto container"
git push

Watch Your Build

When changes are made to containers.git in your Factory sources, a new Target is built by our CI system. Devices that are registered to your Factory will be able to see this Target and conditionally update to it, depending on their device configuration.

Device Configuration

Once the Target is built successfully, any devices that are registered to the Factory will begin updating to this new Target. The app mosquitto that has been defined will be available for usage in this Target. This can be verified by running:

fioctl targets list

By default devices will run all applications that are defined in the containers.git repository and therefore available in the latest Target. This behavior can be changed by enabling only specific applications. Read Enabling/Disabling Apps to learn how.

About Targets¶

Targets are a reference to a platform image and docker applications.

There are four git repositories provided by the factory in https://source.foundries.io/factories/<factory>/:

ci-scripts.git Configures your factory branches - factory-config.yml
containers.git Contains the source code for your Docker-Compose Apps
lmp-manifest.git Open Embedded/Yocto Project manifest for your platform build
meta-subscriber-overrides.git Open Embedded/Yocto Project layer which overrides the Foundries.io Linux microPlatform

When developers push code, the FoundriesFactory produces a new target and adds a tag to that target based on the logic in factory-config.yml in the ci-scripts.git repo. In most cases this tag relates to the branch of meta-subscriber-overrides.git or containers.git where the change originated. Examples would be master or devel. Any registered devices following the same tag will update and install this new target. At a later point, a target’s tags can be added or removed manually by using the fioctl targets tag command.

You can see the available Targets your Factory has produced:

fioctl targets list

CLI Output:

VERSION  TAGS    APPS        HARDWARE IDs
-------  ----    ----        ------------
2        devel               raspberrypi3-64
3        master              raspberrypi3-64
4        master  shellhttpd  raspberrypi3-64

details about Target can be printed by passing its version number to the show subcommand:

fioctl targets show 4

CLI Output:

Tags:   master
CI:     https://ci.foundries.io/projects/gavin/lmp/builds/4/
Source:
        https://source.foundries.io/factories/gavin/lmp-manifest.git/commit/?id=2aaebc4b16c1027c9aae167d6178a8f248027a73
        https://source.foundries.io/factories/gavin/meta-subscriber-overrides.git/commit/?id=19cbbe7b890eafed4d88e1fb13d2d61ecef8f3e5
        https://source.foundries.io/factories/gavin/containers.git/commit/?id=6a2ef8d1dbab0db634c52950ae4a7c18494021b2

TARGET NAME            OSTREE HASH - SHA256
-----------            --------------------
raspberrypi3-64-lmp-4  1b0df36794efc32f1c569c8d61f115b04c4d51caa2fa99c17ec85384ae06518d

DOCKER APP  VERSION
----------  -------
shellhttpd  shellhttpd.dockerapp-4

Completion¶

Now that you’re done, you might want to read Tutorials to see some examples of the things that can be done with your Factory. Additionally, you can read the Reference Manual to learn more about the architecture of FoundriesFactory and the Linux microPlatform.