Please reconsider restricting features in the prebuilt image

[iamspido]

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.

[BeyondVertical]

This!

And also provide images for amd64 - I get (on both sources):

no matching manifest for linux/amd64 in the manifest list entries

[Nuklon]

Yup, typical enshittification behavior. I'll find something else.

[BeyondVertical]

Yup, typical enshittification behavior. I'll find something else.

If you find something similar, let me / us know.

[simono41]

Just testing https://github.com/databasus/databasus

[iamspido]

@simono41 Sadly only PostgreSQL

[simono41]

@simono41 Sadly only PostgreSQL

Nope, it can more :)

[iamspido]

Never 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)

[simono41]

I 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 :)

[BeyondVertical]

Looks great, will check that out too. Thanks for the hint! :)

[iamspido]

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:latest

Repository:

https://github.com/iamspido/nfrastack-container-db-backup

The image is built from the pinned upstream releases of container-base and container-db-backup, with Advanced container functionality enabled through the documented source-build process.

It is available for:

• linux/amd64
• linux/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.

This is an unofficial community build and is not affiliated with or endorsed by Nfrastack.

[tiredofit]

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.

[iamspido]

Thanks for the clarification, and I completely understand where you're coming from.

There was no intention on my side to undermine the project or the way you fund its development. I needed more than three backup jobs for my own infrastructure and initially wasn't aware that reaching out for a key was an option.

Since the source-build path is documented and permitted by the license, I ended up creating a reproducible build for my own use and publishing it in case it is useful to others with the same requirement.

I'll make sure the repository clearly states that it is an unofficial build, links back to the upstream project, and encourages users who rely on the software to support the original project and its development.

I also appreciate the amount of work involved in maintaining this project and the many other images you maintain. Thanks for continuing to make them available.

[falkheiland]

imho its rather sketchy to have the docker image feature restricted. if you want to monetize the project, fine do it and set another license then. this would be the honest approach. its not even in the readme what "advanced features" is, apparently more the 3 jobs? is now "advanced".