Emiliano Suñé

Having the dedicated chart would definitely be a step forward as it would simplify deployment and updates to deployed instances. I'd be happy to review the PR when submitted. One...

@sondrelg we are not _currently_ building multi-arch, just `amd64` (as far as I can remember) - good to know though. In our case, it appears that layers required by tagged...

> How are you building images? If you run `docker inspect ghcr.io/{org}/{package name}:{tag}` I suspect you might at least see an associated manifest for new builds - is that right?...

I just had to manually rebuild and push an image for which I was getting the manifest unknown issue: ```bash $ docker pull ghcr.io/bcgov/traction-plugins-acapy:0.5.0 0.5.0: Pulling from bcgov/traction-plugins-acapy What's next:...

> I am facing the same problem. Any pointers how to fix? Basically all tagged images are broken with Unknown manifest We had to stop using this action as I...

I agree with @jamshale, given the discovery and the possibility that wrapping the required steps in a `transaction` will heavily mitigate or solve the issue I would at least wait...

If I got it right, I agree that updating the docs to use the newer/up-to-date method (containerized cli) is probably the best way forward.

> We'll need to manually create the tags and releases by commit id after forking. The existing images are still available after moving the repo. This is only to create...

I didn't even know this setting/option existed 😅. My understanding was that the base wallet would always ONLY deal with tenant provisioning tasks and nothing else, so the decorators were...

Taking a stab at this since it was brought up at today's maintainers meeting