Closed nelsongraca closed 6 months ago
There seems to have been a change upstream which is causing issues starting at version v5.52
.
I removed those images from the registry and tagged a previous release w/ latest
until this is resolved.
Pulling the latest image now should clear the error.
-Markus
thank you
On Tue, 27 Feb 2024, 21:48 Markus Küffner, @.***> wrote:
There seems to have been a change upstream which is causing issues starting at version v5.52. I removed those images from the registry and tagged a previous release w/ latest until this is resolved.
Pulling the latest image now should clear the error.
-Markus
— Reply to this email directly, view it on GitHub https://github.com/mkuf/prind/issues/117#issuecomment-1967665194, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKSJ3A44SNHWRWI2XML3UDYVZIDFAVCNFSM6AAAAABD4UTGAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRXGY3DKMJZGQ . You are receiving this because you authored the thread.Message ID: @.***>
Is it possible that reverting latest broke arm64? According to Docker Hub the latest tag only supports amd64.
Yes, that was an oversight from my side. I pulled the last working image on my linux/amd64 machine, tagged it as latest and pushed it again.
I'll look into it.
Missing architectures have been copied, latest
is now available for all platforms again.
The underlying issue has been fixed w/ https://github.com/mkuf/prind/commit/4672f87bd0f4ac8641aa0f6ec57f385c17b96c23
Fresh images are currently being built and pushed to the registry.
been using this for quite some time, but ustreamer has stopped working.