Skip to content

[FEAT] Documentation: Specify version of MariaDB as requirement #304

Closed

Description

@mo-st

Is this a new feature request?

  • I have searched the existing issues

Wanted change

Hi and thank you for your immense work.

You specify that a MariaDB instance is required, but there is no information about the required version (major or minor).
Questions that result from this: Should I pin it? Is it safe to roll with :latest?
Can I install any version of the LSIO mariadb image? Can I update at any time to any version?

Thank you for your consideration.

Reason for change

I think the documentation would be improved by providing this information.
Users would be able to confidently run and update both components without breakage.

Proposed code change

Bookstack lists in it's requirements version MariaDB >= 10.6 at the time of writing.

Activity

  1. github-actions commented on Nov 14, 2026

    @github-actions

    Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

  2. aptalca commented on Nov 14, 2026

    @aptalca
    Member

    We recommend our mariadb image. Our mariadb image does not support older major/minor versions, only the latest.

    Whether you want to pin is up to you, but we recommend regular image updates (attended, with proper backups that would allow a rollback if necessary)

  3. mo-st commented on Nov 14, 2026

    @mo-st
    Author

    I'm aware of the update ideals of LSIO, and while I personally prefer automating minor updates and only bothering with manual on major ones, this isn't really the point I was getting at, I'll try to make it clearer what I meant and edit the questions.

    My point was that providing the user with a version requirement information allows them to make proper decisions on updating for themselves. It would be a benefit to see this right away, no matter how you personally choose to update your services.

    Was that more understandable?

  4. aptalca commented on Nov 14, 2026

    @aptalca
    Member

    Version requirement comes from upstream. You can check there if you're curious.

    Our version recommendation (for our image) is to use the latest version, which is the only supported version as that's the only one that gets dependency updates.

    We're not going add a blurb to our readme about any other version because that would go against the above recommendation and would only confuse the users.

    With regards to automating updates, we strongly recommend against it, as well as relying on upstream semver: https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time#semver-info

  5. mo-st commented on Nov 14, 2026

    @mo-st
    Author

    Thank you for taking your time to reply and the link. I can understand your decision on not providing any requirement information and pointing the user to upstream.

    While I personally think it would've been helpful, I'll close the request then as you don't agree and provided valid reasons.

    I'll gladly read your insights on updating practices, for now let's agree to disagree, maybe I'll change my mind after the read.

    Thanks again for your work and have a good weekend

  6. moved this from Issues to Done in Issue & PR Trackeron Nov 14, 2026
  7. mo-st commented on Nov 14, 2026

    @mo-st
    Author

    That was an interesting read and I understand the mental model for LSIO images specifically a lot better now. I agree semantic versioning would be misleading to the user and unsustainable for you.
    My stance originated more on software versioning and update practices as a whole and didn't take your specific challenges into account.

    I'll consider not auto updating LSIO images in the future and think twice about choosing one, knowing the manual work it will entail, especially for upstreams like these, which release often (and may need to be updates for security reasons).

    Food for thought to be sure. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions