Update base image to AlmaLinux 10 non-minimal

[amotl]

About

Better safe than sorry, use the non-minimal AlmaLinux image until we validated the minimal variant on all environments thoroughly.

@goat-ssh reported:

gcp: /crate/bin/crate: line 199: hostname: command not found 
....
ERROR: setting [node.attr.zone] must not be empty

NB: Please merge at your disposal.

[mfussenegger]

hostname is not used by the bin/crate script, where is that coming from?

In general only the documented commands (crate and crash) are supported.

If hostname or other commands are required for some cases, we'd need test cases and docs for it, otherwise this is bound to regress again in the future.

[amotl]

Yes. I experimented with minimal images when transitioning from CentOS, and decided against them due to too many possible obstacles and reported about it.

Even if the hostname command is present, other things might be missing that possibly lead to other subtle problems. Minimal images should not be used lightheartedly, in the same spirit why we also don't use AlpineLinux.

[goat-ssh]

Here is the code requiring hostname https://github.com/crate/crate-operator/blob/master/crate/operator/create.py#L437-L456
"-Cnode.name": f"{crate_node_name_prefix}$(hostname | rev | cut -d- -f1 | rev)",

[amotl]

@matriv reported this patch also fixes this issue:

• Impossible to run CrateDB 5.9.9 in Docker crate#17354

[mfussenegger]

Here is the code requiring hostname https://github.com/crate/crate-operator/blob/master/crate/operator/create.py#L437-L456 "-Cnode.name": f"{crate_node_name_prefix}$(hostname | rev | cut -d- -f1 | rev)",

This is even worse because it additionally relies on bin/crate doing shell expansion on the argument, which is more an accident than intentionally supported.
We might break that in the future.

Switching to non-minimal is okay as a quickfix, but we can't keep supporting any unknowns. Undocumented = Unsupported

[seut]

@matriv reported this patch also fixes this issue:

* [Impossible to run CrateDB 5.9.9 in Docker crate#17354](https://github.com/crate/crate/issues/17354)

This issue is already fixed by c83963c.

[matriv]

So, for the time being should we merge this and re-release the docker image, to remedy the situation?
Or should we wait to fix the issue in our tooling?

[goat-ssh]

@mfussenegger can you spot a more viable way of getting this w/o shell expansion ?
Jfyi, we're also relying on curl being present on the image: https://github.com/crate/crate-operator/blob/master/crate/operator/create.py#L505-L523

[amotl]

I experimented with minimal images when transitioning from CentOS, and decided against them due to too many possible obstacles and reported about it.

I am proposing to merge this, in oder to fix any downstream problems, and perform a baseline image update in a more controlled environment, accompanying a solid testing procedure ¹.

Footnotes

1. Possibly also add relevant software tests, seconding @mfussenegger's advise. ↩