docs: update readme from mariadb with port binding, tags, remove double spaces and informations

[felipementel]

This pull request includes updates to the mariadb documentation and configuration files to improve clarity and compatibility, as well as to specify versions for certain images.

Documentation improvements:

• mariadb/content.md: Added an important note about the %%IMAGE%% tags to highlight the latest and lts versions.
• mariadb/content.md: Updated the Docker compose command to use docker compose instead of docker-compose for consistency with the latest Docker CLI.
• mariadb/content.md: Added a section on port binding to explain how to expose the container port to the host port using the -p argument in the docker run command.

Configuration updates:

• mariadb/stack.yml: Specified the image versions for mariadb and adminer to ensure consistency and compatibility. The mariadb image is updated to 11.7-ubi and adminer to 4.17.1.
• mariadb/stack.yml: Remove docker compose version on file header - the docker compose version is obsolete

[tianon]

I've left a few notes 👍

I'll also explicitly CC the mariadb image maintainers: @grooverdan @dbart @fauust

[tianon]

These really specific version numbers are likely to bitrot quickly, so we don't typically suggest being so particular unless it's actually necessary to be.

(Also, see the prior note about exposed database ports.)

[grooverdan]

especially with 11.7 as a short term support release. Perhaps use a lts /lts-ubi tag and I guess something for adminer. The purpose of compose files was self contained, so especially with something link adminer, exposing ports seems unnecessary.

On env variables including something like MARIADB_AUTO_UPGRADE=1 would smooth the upgrade paths.

I wouldn't mind seeing the healthcheck and service dependency like https://mariadb.com/kb/en/using-healthcheck-sh/#compose-file-example here as a practically of showing of getting the database up before the services that connect to it (and might fail if they can't connect). (edit: assuming docker stack compatibility).

[felipementel]

These really specific version numbers are likely to bitrot quickly, so we don't typically suggest being so particular unless it's actually necessary to be.

(Also, see the prior note about exposed database ports.)

updated.

especially with 11.7 as a short term support release. Perhaps use a lts /lts-ubi tag and I guess something for adminer. The purpose of compose files was self contained, so especially with something link adminer, exposing ports seems unnecessary.

On env variables including something like MARIADB_AUTO_UPGRADE=1 would smooth the upgrade paths.

I wouldn't mind seeing the healthcheck and service dependency like https://mariadb.com/kb/en/using-healthcheck-sh/#compose-file-example here as a practically of showing of getting the database up before the services that connect to it (and might fail if they can't connect). (edit: assuming docker stack compatibility).

I like the idea.

I think another section, with this more complete example, would be better. Then we can have a more basic section and a more advanced one.

[tianon]

This thread isn't resolved (references in stack.yml are still too-specific).

[grooverdan]

thanks for the cleanup.

[felipementel]

@tianon, @grooverdan
There are other points to yours check?

[felipementel]

Do I need to make any further adjustments for analysis and approval?

[grooverdan]

sorry for delay. I'll get to it next week.

[felipementel]

@grooverdan
What can I do to merge this pull request?

[grooverdan]

previous comments remain unaddressed.

[grooverdan]

there's still specific versions here.

[grooverdan]

MARIADB_AUTO_UPGRADE=1 isn't there in env

[grooverdan]

while I do generally like the idea of pinning versions, on a UI is it important? With this versioned pinned the updates to this are going to be quite frequent - current adminer versions: https://github.com/docker-library/official-images/blob/master/library/adminer