Docker image OCI labels

[tigattack]

Describe what you are trying to accomplish and why in non technical terms

I want to be able to access a (ideally standardised, i.e. OCI) set of labels for the Frigate images so that I can reference them in automations. Specifically, I'm working on making my Ansible role for Frigate a little more robust, and being able to reference labels such as org.opencontainers.image.version would be very useful.

Describe the solution you'd like

Labels (again, ideally OCI labels) added to the Frigate Docker images.

This is trivial with docker/metadata-action, and I was actually going to create a PR, but I see that the release workflow is quite non-standard when it comes to typical GitHub Actions Docker build/push workflows.

I thought I'd create this issue to open some discussion on the matter before I consider a PR with the sort of changes that would be necessary based on my understanding of the existing workflow(s), as it could be disruptive (in terms of the maintainers' preferences, hopefully not in terms of functionality!)

[NickM-27]

What changes would be involved in doing that?

[tigattack]

docker/metadata-action is a simple way to achieve this, however I don't think this would be compatible with the current release.yml workflow using skopeo. Personally, I'd be looking at rewriting the workflow to use docker/build-push-action using labels/annotations generated by docker/metadata-action.

The reason I didn't jump straight into doing this & opening a PR is I wasn't sure if I was missing any context on why release.yml is designed to use skopeo rather than the typical docker/build-push-action with cache (to reduce build time/avoid rebuilding almost the same image as was built for the most recent commit by ci.yml).

[NickM-27]

Yeah, the current skopeo workflow which involves combing docker images from different tags is a high priority item to keep, not something we would want to be removed

[NickM-27]

The Frigate CI already uses cache without any issues

[halkeye]

okay, in theory #19921 should do this
🤞

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tigattack]

Thanks a lot for the PR! Hopefully someone has a chance to look over it soon.