Containly 2.7.4: backups work again even when the helper image was removed

Containly 2.7.4 is a small fix release. It fixes backups failing with "No such image: alpine:latest" and centres the empty states.

Backups failing with "No such image: alpine:latest" (fix)

• Containly checked its backup helper image only once per process start. When the image was removed from the host later, for example by docker image prune or a cleanup, Containly never pulled it again, and every scheduled and manual backup failed with (HTTP code 404) no such container - No such image: alpine:latest until Containly was restarted.
• Containly now checks the helper image before every use and pulls it again when it is missing. If it disappears right between the check and the start of the helper container, Containly pulls it once more and retries.
• The helper containers for backups, restores, the folder picker and volume file access no longer use the moving alpine:latest tag but a pinned Alpine 3.22.2 image (by digest, for amd64 and arm64). They keep their Containly helper label.

Empty states centred

• Empty states (for example Updates > "All up to date", empty lists, no search hits) now sit as one block in the centre of the free area instead of top-left, on every page, on desktop and phone, light and dark.

Update
docker compose pull && docker compose up -d (or the self-update under Settings > Version and licence).

Still on an older version and backups fail with this message? Running docker pull alpine:latest on the host helps right away; the update fixes the cause.

Release notes: https://github.com/amslertec/containly/releases/tag/v2.7.4