Zincati updates for ostree container images

Ask Fedora
,
1

How to make Zincati work with container images update?

I have updated images on my own container registry, how do I use Zincati to auto update my machines when there’s a new image on my container registry? I’m currently checking the Cincinnati protocol which outputs in /v1/graph. This is the sample output for Cincinnati graph

{
  "nodes": [
    {
      "version": "latest",
      "metadata": {
        "org.fedoraproject.coreos.scheme": "checksum"
        "org.fedoraproject.coreos.releases.age_index": "0",
      },
      "payload": "7c23c4735fb3c541586f0a4d3ca956ef93ef7d76f00a19bccf51460bafa7ee97"
    },
    {
      "version": "latest",
      "metadata": {
        "org.fedoraproject.coreos.scheme": "checksum",
        "org.fedoraproject.coreos.releases.age_index": "1"
      },
      "payload": "8cffe35be831fa2601d315002cb39fb22509a4e7d3db10e61f880523f69b3bf6"
    }
  ],
  "edges": [
    [
      0,
      1
    ]
  ]
}

How do I make this work for containers? This is only for ostree repos right the version and payload. I want to make a quite simple graph update

2

Zincati does not work with container images right now. This is tracked in Making Cincinnati updates work with ostree containers · Issue #1263 · coreos/fedora-coreos-tracker · GitHub.

Related discussions:

This is part of the reasons that while we publish those images right now, we don’t recommend nor document it yet as we don’t have the full update story like we have right now.

1 Like
3

Thanks for the clarification as I thought so it’s not yet okay for the public. I’ll track and watch the GH issues for this one. Thanks mate!