Container installation instructions for podman may lead users into unintended updates

[AllegraCodes]

The container installation examples do not suggest to specify a tag, so the 'latest' tag is used by default. A common pitfall for new users is to auto-update their containers or manually pull a new image unaware of a major update to 'latest'. Then they are frustrated to find they can't revert without a backup.

I would suggest recommending the use of a patch version tag (eg 10.11.0) and showing in the example how to specify it after the image. You could even point out that the team helpfully maintains multiple tags to specify the update level you are comfortable with (eg 10.11). If this is undesired for some reason, a short warning not to pull a new image without checking for changes would suffice.

[AllegraCodes]

I suppose this is really only an issue with the podman instructions, which suggests the use of the autoupdate label. Otherwise updates are kind of a separate issue from installation.