Clark Boylan 1c1cc12ab5 Refactor check for new container images
Two of our services (gitea and jitsi meet) need to take special action
when docker-compose pull updates images and cannot rely on a basic up -d
after a pull. Previously we checked the stderr output of docker-compose
for a string indicating at least one image was updated to determine if
any images updated. The problem with this approach is docker compose is
less verbose than docker-compose and does not give us this information.

In preparation for our slow but eventual migration to docker compose for
these services update the new image check process. Now we perform a
docker image listing before and after the pull and compare the emitted
image ID lists. Image ids should change when we pull new images and
their sort order should be stable command to command (they are sorted by
image age).

Change-Id: I7e9ca8cc7bc0454dcca82c02b6913d81aa4927b3
2024-12-13 07:55:22 -08:00
..
2022-09-16 12:10:00 -07:00
2021-03-18 11:55:02 -07:00

Install, configure, and run jitsi-meet.

Note that the Jitsi Meet docker images supply template files in /defaults on the image. These template files are used to generate configs in /config on the image (/var/jitsi-meet on the host) using the docker-compose .env file and its vars.

If we need to make changes to the configs we need to bind mount in a modified template file so that the config file generation produces what we expect. If we try to write the configs files ourselves then when jitsi meet restarts we will lose those configs until the next ansible run.