The error is "The key(s) in the keyring
/etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg are ignored
as the file is not readable by user '_apt' executing apt-key" but it
looks like the files are owned by root:root and the permissiosn is 0644
so I'm not sure what's the issue here. Let's see.

I want to run it remotely on my Kodi.

The image fails to build with the latest stable release (Bullseye) and
since I'm using it anymore, I'm not going to invest time in figuring
this out (it's either going back a version and seeing if that works or
removing the image altogether).

Those jobs are not always in the workflow and that makes the workflow
invalid in those cases. Since the build and push already happens before
those jobs will use the newer base images anyway.

Some images are base images for other images. There's a need to build
the base images first.

- Use the environment variables (like APACHE_RUN_USER or APACHE_LOG_DIR)
  during the build, so now they're set earlier.
- Add the APACHE_LOCK_DIR.

- Use the containerfiles templates.
- The repo was renamed as part of a refactor.

- New, updated or migrated pre-commit hooks.
- Fix found issues.

I'm getting 401 or 403 with the project set.

Without the CONTEXT variable, the rules for push jobs was broken and
always triggered. This also pulled in the dependency jobs. I don't see a
way to avoid defining the CONTEXT variable in both build and push jobs.

Same as the buster image, but bullseye.

Both latest and buster tags.

- Notify on scheduled pipeline failures.
- Seperate the IMAGE and CONTEXT variables. Allow building where the 2
don't match (planning for httpd/buster and httpd/bullseye).