Repository navigation
Please reconsider restricting features in the prebuilt image #485
Description
Activity
This!
And also provide images for amd64 - I get (on both sources):
no matching manifest for linux/amd64 in the manifest list entriesReacted by bjekel and Simon RiegerYup, typical enshittification behavior. I'll find something else.
Yup, typical enshittification behavior. I'll find something else.
If you find something similar, let me / us know.
Reacted by mr-flibbleJust testing https://github.com/databasus/databasus
Reacted by BeyondVerticalNever mind, I had only seen the title.
According to the README, the following databases are supported:
💾 Supported databases
- PostgreSQL: versions 14, 15, 16, 17, and 18 (physical and logical backups)
- MySQL: versions 5.7 and 8 (logical backups only)
- MariaDB: versions 10, 11, and 12 (logical backups only)
- MongoDB: versions 4.2+, 5, 6, 7, and 8 (logical backups only)
Reacted by Simon RiegerI just moved my entire server environment with 24 databases each with MariaDB or PostgreSQL to Databasus in just 2 hours.
I can only recommend the software :)
Looks great, will check that out too. Thanks for the hint! :)
I have published an unofficial source-built image that does not have the three-backup-job limitation and does not require an unlock code:
ghcr.io/iamspido/nfrastack-container-db-backup:latestRepository:
https://github.com/iamspido/nfrastack-container-db-backup
The image is built from the pinned upstream releases of
container-baseandcontainer-db-backup, with Advanced container functionality enabled through the documented source-build process.It is available for:
linux/amd64linux/arm64
Example:
services: db-backup: image: ghcr.io/iamspido/nfrastack-container-db-backup:latest
I am currently running it with ten configured backup jobs successfully.
The image also includes a temporary fix for the MySQL client regression in
4.9.0, where the Oracle MySQL client was called with the unsupported--skip-ssloption instead of--ssl-mode=DISABLED.This is an unofficial community build and is not affiliated with or endorsed by Nfrastack.
Hi, I'm moving this to discussions as I don't deem this as a bug report.
Under the terms of the MIT license your usage is fully compliant. While I would have preferred you reach out to me and discuss things like others have and be provided a key back to them after talking, I understand you are doing just what needs to be done to support your operations.
I, who as an unemployed person hand write, and maintain this and ~100 other images, rely on funding to continue supporting and maintaining these images. Feel free to send over any supporters or clients my way, I'm happy to talk.
- locked and limited conversation to collaborators
on Aug 6, 2026
The latest version (4.9.0) appears to restrict functionality in the prebuilt container image. Advanced features and certain environment variables now require an unlock code.
I want to provide clear feedback: I do not like this direction, and I believe it is the wrong approach for this project.
One of the main advantages of container-db-backup has been that it provides a flexible and transparent self-hosted backup solution. Restricting existing configuration options in the publicly available image introduces unnecessary friction, complicates upgrades, and makes the project less suitable for automated and reproducible deployments.
This is particularly problematic for a backup tool, where reliability, predictable configuration, and long-term maintainability are essential.
I understand the need to fund ongoing development, but limiting the functionality of the prebuilt image is, in my opinion, the wrong trade-off. Paid support, sponsorships, consulting, or additional enterprise services would be preferable to restricting core configuration functionality.
Please reconsider this decision and provide a fully functional community image without feature restrictions.