from alam@lemmy.world to selfhosted@lemmy.world on 26 Jan 12:16
https://lemmy.world/post/42192212
Hello everyone,
As mentioned earlier in this post: lemmy.world/post/41783666, we lost access to our bentopdf Docker Hub account. Despite contacting Docker Hub support, the issue has remained unresolved for over 10 days. As a result, we have migrated to a new Docker Hub account.
The images under bentopdf/bentopdf are no longer maintained by us. The new official Docker Hub repository for BentoPDF is bentopdfteam/bentopdf.
Additionally, GHCR (GitHub Container Registry) is now our recommended container registry, and we have added support for Podman Quadlet.
Over the next few updates, we will be working on releasing the following features: • PDF to PDF/X conversion • Bates Numbering • PKCS#11 support • PDF text editing support
Thank you for your patience and continued support.
#selfhosted
threaded - newest
Go, BentoPDF! A shame this stuff cost you time and energy better spent elsewhere, but it’s just a small hiccup for a project with legs!
Thank you! (:
That’s a real bitch if you’re running watchtower and have the latest tag set. If you aren’t watching this drama, it’s an easy pwn for whoever took it over.
Docker Hub needs to get their shit together.
That’s an interesting point, I’m kind of surprised if docker images don’t have any measures to prevent malicious takeovers.
Not sure what Docker Hub has, but as sys admin you can pin to a specific 256sha, so that specific image can’t be taken over. However that conflicts with the idea of just running Watchtower.
Does anyone know how it affects the people using Bento through TrueNAS apps?
Truenas apps are mere docker containers configured by someone else in the community.
If you turn them into a customized app, you gain all the docker options control and can change the image. It’s all up to the app maintainer to switch to the correct image, or yourself to do it manually.
I see, thank you.