docker containers for the various parts

[bnordgren]

• tile server
• web application
• aprsd
• direwolf
• gpsd

[bnordgren]

I now have a docker container for arm64 and armhf which contains all three functional units of software. Many of the important configuration files have been exposed in the docker build directory, and are copied in to the image when it is built.

Separately, I also have a container with just the mapcache (tile server.) The tile server has been running on my Pi Zero and seems quite capable of seeding the tile cache.

Making a container image for just the aprsd part should also be pretty easy.

Isolating the webapp will be tricky because I'm using the supplied binary packages, and the webapp depends on the other two pieces of software. May need to repackage or just install from source.

[bnordgren]

Mental note: currently (locally) my polaric images are tagged as "polaric-webapp-xxxxx" where xxxxx is the architecture. Before publishing on dockerhub, make sure to rename them to polaric-server-xxxxx.

[bnordgren]

Note that the docker container running jsvc (e.g., polaric-aprsd) needs to have extra capabilities allowed. For my all-in-one container, mistakenly named "webapp" as noted above, this is:

docker run --name polaric -ti -p 80:80 --cap-add DAC_READ_SEARCH polaric-webapp-arm64 bash

[bnordgren]

getting sound into the direwolf container was not obvious. long story short:

docker run -ti --net polaric_net  --name direwolf --rm --device /dev/snd:/dev/snd   direwolf-arm64

• This is from: https://github.com/danielchalef/jasper-docker
• Ignore all Pulseaudio advice, this in particular.

[bnordgren]

docker run --name polaric --cap-add DAC_READ_SEARCH -d -p 80:80 --net aprs-box -v /home/alarm/mapdata:/var/cache/mapcache polaric-server-arm64

[bnordgren]

Put the following in /etc/systemd/system/docker-polaric_server.service to make the container named "polaric" start automatically and restart if it ever dies:

[Unit]
Description=Polaric server container
Requires=docker.service
After=docker.service

[Service]
Restart=always
ExecStart=/usr/bin/docker start -a polaric
ExecStop=/usr/bin/docker stop -t 2 polaric

[Install]
WantedBy=default.target

You have to have a container named polaric, though.

[bnordgren]

The docker container requires read/write access to the /sys/class/gpio tree to make PTT work.

docker run -ti --device /sys/class/gpio:/sys/class/gpio direwolf-arm64

[bnordgren]

The docker container requires read/write access to the /sys/class/gpio and /sys/devices/platform trees to make PTT work. Combined with the access to the sound devices (above):

docker run -ti -v /sys/class/gpio:/sys/class/gpio -v /sys/devices/platform:/sys/devices/platform --device /dev/snd:/dev/snd direwolf-arm64

[bnordgren]

Cleaning up the docker build process a little bit, I'm coming to the following revelations:

• It will never be as simple as a "docker pull" because there is too much configuration.
• It can be as simple as "git clone && configure && docker build"
• I can use a single Dockerfile for multiple platforms. The primary difference building for an x86_64 desktop, ARM 32 bit (Pi, BeagleBone, etc) and ARM 64 bit (Odroid C2) is the FROM line. Everything else is the same.

The main problem I have so far is that the debian jessie build for 64 bit intel/amd architectures stalls out while installing a dependency, whereas debian jessie for aarch64 works just fine. Ubuntu 16.04 for intel/amd works just fine.