Updating the project¶

There are two different update sources: the IOTstack project (github.com) and Docker image registries (e.g. hub.docker.com). Both the initial stack creation and updates use both of these. Initial creation is a bit simpler, as the intermediate steps are done automatically. For a full update they need to be performed explicitly. To illustrate the steps and artifacts of the update process:

flowchart TD
  GIT[github.com/sensorsiot/IOTstack.git]
  GIT       --- GITPULL([$ git pull -r])
  GITPULL   --> TEMPLATES["~/IOTstack/.templates"]
  TEMPLATES --- MENU([$ ./menu.sh -> Build stack])
  MENU      --> COMPOSE["~/IOTstack/docker-compose.yml
                         ~/IOTstack/.templates/*/Dockerfile
                         ~/IOTstack/services/*/Dockerfile"]
  COMPOSE   --- UP(["$ docker-compose up --build -d"])

  HUB[hub.docker.com images and tags]
  HUB       --- PULL([$ docker-compose pull\n$ docker-compose build --pull --no-cache])
  COMPOSE   --- PULL
  PULL      --> CACHE[local Docker image cache]
  CACHE     --- UP

  UP        --> CONTAINER[recreated Docker containers based on the latest cached images]

  classDef command fill:#9996,stroke-width:0px
  class GITPULL,MENU,UP,PULL command

Minor details fudged in the graph

In order to keep the graph simple, some minor details were left unprecise:

$ docker-compose pull will read docker-compose.yml, in order to know what image tags to check for updates.
$ docker-compose build --pull --no-cache will use docker-compose.yml to find which of the "build:" sources are in use:
- ~/IOTstack/.templates/*/Dockerfile
- ~/IOTstack/services/*/Dockerfile
- remote repositories with Dockerfiles
and pull Docker images referenced in these while building.
$ docker-compose up --build -d may not require the "--build"-flag, but having it won't hurt (and may help keep some corner-case problems away, docker may be a bit finicky).

Backup and rollback¶

The usual way of backing up just your ~/IOTstack contents isn't sufficient for a 100% identical restore. Some containers may have local ephemeral modifications that will be lost when they're recreated. Currently running containers may be based on now outdated images. Recreating a container using an old image is tricky. The local Docker image cache can't easily be restored to the same state with old images and old tag references. The docker pull will fetch the latest images, but it's not unheard of that the latest image may break something.

Thus to guarantee a successful rollback to the pre-update state, you have to shutdown your RPi and save a complete disk image backup of its storage using another machine.

For a hobby project, not having a perfect rollback may be a risk you're willing to take. Usually image problems will have fixes/workarounds within a day.

Update Raspberry Pi OS¶

You should keep your Raspberry Pi up-to-date. Despite the word "container" suggesting that containers are fully self-contained, they sometimes depend on operating system components (WireGuard is an example).

$ sudo apt update
$ sudo apt upgrade -y

Recommended: Update only Docker images¶

When you built the stack using the menu, it created the Docker Compose file docker-compose.yml. This file and any used build instructions (Dockerfiles), use image name and tag references to images on hub.docker.com or other registries. An undefined tag defaults to :latest. When Docker is told to pull updated images, it will download the images into the local cache, based upon what is currently stored at the registry for the used names and tags.

Updating the IOTstack project templates and recreating your docker-compose.yml isn't usually necessary. Doing so isn't likely to provide much benefits, and may actually break something. A full update is only recommended when there is a new feature or change you need.

Recommended update procedure

Shutdown your RPi, remove the storage medium and do a full backup image of the storage to another machine. Reattach the storage back and power up your RPi.
NOTE: To skip this step may cause days of downtime as you debug a problem or wait for fixes.
Get latest images from the web:
```
$ docker-compose pull
```
Rebuild localy created images based on new parent images:
```
$ docker-compose build --pull --no-cache
```
Note: this may not do anything, depending on your selected services.
Update(recreate) containers that have new images:
```
$ docker-compose up --build -d
```

If a service fails to start after it's updated, especially if you are updating frequently, wait for a few hours and repeat the update procedure. Sometimes bad releases are published to hub.docker.com, but they are usually fixed in under half a day. Of course you are always welcome to report the problem to our Discord server. Usually someone else has encountered the same problem and reported the fix.

Full update¶

Periodically updates are made to project which include new or updated container template, changes to backups or additional features. To evaluate if this is really needed, see the changelog or merged pull requests. To apply all these changes all service definitions are recreated. As a drawback, this will wipe any custom changes to docker-compose.yml, may change semantics or even require manual migration steps.

Breaking update

A change done 2022-01-18 will require manual steps or you may get an error like:
ERROR: Service "influxdb" uses an undefined network "iotstack_nw"

Full update steps:

Shutdown your RPi, remove the storage medium and do a full backup image of the storage to another machine. Reattach the storage back and power up your RPi.
NOTE: To skip this step may cause days of downtime as you debug a problem or wait for fixes.
check git status --untracked-files no for any local changes you may have made to project files. For any listed changes, either:
1. Save and preserve your change by doing a local commit: git commit -m "local customization" -- path/to/changed_file, or
2. Revert it using: git checkout -- path/to/changed_file
Update project files from github: git pull -r origin master
Save your current compose file: cp docker-compose.yml docker-compose.yml.bak. NOTE: this is really useful, as the next step will overwrite all your previous manual changes to docker-compose.yml.
Recreate the compose file and Dockerfile:s: ./menu.sh, select Build Stack, for each of your selected services: de- and re-select it, press enter to build, and then exit.
check the changes for obvious errors (e.g. passwords): diff docker-compose.yml docker-compose.yml.bak
Perform the Docker image update procedure: console $ docker-compose pull $ docker-compose build --pull --no-cache $ docker-compose up --build -d

Troubleshooting: if a container fails to start after update¶

try restarting the whole stack: docker-compose restart
Check log output of the failing service: docker-compose logs *service-name*
- try googling and fixing problems in docker-compose.yml manually.
check how the container definitions have changed: diff docker-compose.yml docker-compose.yml.bak
try rebuilding your complete stack from scratch:
1. check that you have a backup.
2. stop and remove Docker containers: docker-compose down
3. remove all menu generated files: rm -r docker-compose.yml services
4. recreate the stack: ./menu.sh, select Build Stack, select all your services, press enter to build, and then exit.
5. try starting: docker-compose up -d
Go to the IOTstack Discord and describe your problem. We're happy to help.

Warning

If you ran git checkout -- 'git ls-files -m' as suggested in the old wiki entry then please check your duck.sh because it removed your domain and token

Git offers build in functionality to fetch the latest changes.

git pull origin master will fetch the latest changes from GitHub without overwriting files that you have modified yourself. If you have done a local commit then your project may to handle a merge conflict.

This can be verified by running git status. You can ignore if it reports duck.sh as being modified.

Should you have any modified scripts or templates they can be reset to the latest version with git checkout -- scripts/ .templates/

With the new latest version of the project you can now use the menu to build your stack. If there is a particular container you would like to update its template then you can select that at the overwrite option for your container. You have the choice to not to overwrite, preserve env files or to completely overwrite any changes (passwords)

After your stack had been rebuild you can run docker-compose up -d to pull in the latest changes. If you have not update your images in a while consider running the ./scripts/update.sh to get the latest version of the image from Docker hub as well