# How to setup BCO via Docker

WARNING

This installation instruction is in an early stage and any feedback is welcome!

# Define Default User

If you want to use the current user as the default one, just execute the following command. Otherwise store the name of the default user in the following variable:

export DEFAULT_USER=$(whoami)

# Setup Docker Environment

Follow the official setup guidelines at Docker Docs
- Short summary for the pi:
  1. curl -fsSL https://get.docker.com -o get-docker.sh
  2. sudo sh get-docker.sh
Add default user to docker group

sudo usermod -aG docker ${DEFAULT_USER}

# Spread Setup

# Create Docker Container

sudo docker run \
        --name spread \
        --net=host \
        -d \
        --restart=always \
        openbaseorg/spread:latest

1
2
3
4
5
6

# Openhab Setup

Create a new openHAB user + group

sudo adduser --system --shell /usr/sbin/nologin openhab
sudo addgroup --system openhab
sudo usermod -a -G openhab openhab

1
2
3

Enable the openHAB user to access usb gateways such as zwave or zigbee sticks

sudo usermod -a -G dialout openhab
sudo usermod -a -G tty openhab

1
2

# Add the default user to the openHAB group

sudo usermod -a -G openhab ${DEFAULT_USER}

# Setup Z-Wave USB Stick

INFO

Skip this step if you do not have a Z-Wave USB Stick!

At this point, make sure your Z-Wave USB Stick is plugged in and that it is available under the following path:

export ZWAVE_STICK=--device=/dev/ttyACM0

# Create Openhab Docker

sudo docker run \
    --name openhab \
    --net=host \
    -v /etc/localtime:/etc/localtime:ro \
    -v /etc/timezone:/etc/timezone:ro \
    -v openhab_conf:/openhab/conf \
    -v openhab_userdata:/openhab/userdata \
    -v openhab_addons:/openhab/addons \
    -d \
    -e USER_ID=$(id -u openhab) \
    -e GROUP_ID=$(getent group openhab | cut -d: -f3) \
    --restart=always \
    $ZWAVE_STICK \
    openhab/openhab:2.5.11

1
2
3
4
5
6
7
8
9
10
11
12
13
14

# BCO Setup

# Create BCO user and group

sudo adduser --system --shell /usr/sbin/nologin bco
sudo addgroup --system bco
sudo usermod -a -G bco bco

1
2
3

# Add default user to bco group

sudo usermod -a -G bco ${DEFAULT_USER}

# Create BCO Core Docker

sudo docker run \
    --name bco \
    --net=host \
    --volume /etc/localtime:/etc/localtime:ro \
    --volume /etc/timezone:/etc/timezone:ro \
    --volume bco_data:/home/bco/data \
    --detach \
    --env USER_ID=$(id -u bco) \
    --env GROUP_ID=$(getent group bco | cut -d: -f3) \
    --restart=always \
    -t \
    openbaseorg/bco:experimental

1
2
3
4
5
6
7
8
9
10
11
12

# Create BCO Device Manager Openhab Docker

sudo docker run \
    --name bco-device-manager-openhab \
    --net=host \
    --volume /etc/localtime:/etc/localtime:ro \
    --volume /etc/timezone:/etc/timezone:ro \
    --volume bco_data:/home/bco/data \
    --volume openhab_conf:/etc/openhab2 \
    --detach \
    --env USER_ID=$(id -u bco) \
    --env GROUP_ID=$(getent group bco | cut -d: -f3) \
    --env OPENHAB_GROUP_ID=$(getent group openhab | cut -d: -f3) \
    --restart=always \
    -t \
    openbaseorg/bco-device-manager-openhab:experimental

1
2
3
4
5
6
7
8
9
10
11
12
13
14

# Enable BCO to access the openHAB sitemap directory in order to generate or update sitemaps

Make BCO user a member of the openHAB group

sudo chmod -R g+rwX /var/lib/docker/volumes/openhab_conf/_data/sitemaps
sudo chgrp bco /var/lib/docker/volumes/openhab_conf/_data/sitemaps

1
2

# Setup Portainer as Docker Management Tool

The official installation can be found at: Portainer Doc or use this shortcut:

sudo docker volume create portainer_data
sudo docker run \
    -d -p 8000:8000 \
    -p 9000:9000 \
    --name portainer \
    --restart=always \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v portainer_data:/data portainer/portainer-ce

1
2
3
4
5
6
7
8

After the installation has finished, you can access portainer via port 9000 for example: http://yourhostname:9000

# Setup auto update service with watchtower

Watchtower can be used to automatically keep your docker containers up-to-date. The following modifications has been applied:

WATCHTOWER_CLEANUP cleans up images that has been replaced by newer ones.
WATCHTOWER_INCLUDE_STOPPED even update stopped containers.
WATCHTOWER_TIMEOUT give components more time to perform a proper container shutdown.
-v /etc/timezone:/etc/timezone:ro use the timezone of the hosts system.

Checkout the watchtower documentation for more details.

# Setup Watchtower as a daemon service

Once watchtower is deployed as a daemon service, it will check every 300 seconds for new container images. In case a new image is available, the container will be stopped, updated and started after the update has finished.

Use the following command to setup watchtower as a daemon:

sudo docker run -d \
    --name watchtower \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /etc/timezone:/etc/timezone:ro \
    --env WATCHTOWER_CLEANUP=true \
    --env WATCHTOWER_INCLUDE_STOPPED=true \
    --env WATCHTOWER_TIMEOUT=60 \
    containrrr/watchtower:latest

1
2
3
4
5
6
7
8

# Setup Watchtower as a one shot service

In case you still want to be the one who is in change when updates should be performed, you can setup watchtower as a one shot service. Therefore, updates are only checked in case you manually start the watchtower container. Once started, watchtower will update all containers and stop itself afterwards again.

Use the following command to setup watchtower as aon shot service.

sudo docker run -d \
    --name watchtower \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /etc/timezone:/etc/timezone:ro \
    --env WATCHTOWER_CLEANUP=true \
    --env WATCHTOWER_INCLUDE_STOPPED=true \
    --env WATCHTOWER_TIMEOUT=60 \
    --env WATCHTOWER_RUN_ONCE=true \
    containrrr/watchtower:latest

1
2
3
4
5
6
7
8
9

# Next Step

Now, the docker setup is finished and you can continue with the initial openHAB setup.