Improve documentation: avoid using 'latest' tag for Uyuni containers

[pks2906]

Closes uyuni-project/uyuni#10708

Description

This PR improves the Uyuni documentation by recommending avoiding the use of the latest tag for container images.

Using the latest tag can lead to unintended upgrades and non-reproducible environments when new images are released.

This change adds a new section with examples suggesting the use of fixed version tags instead.

Target branches

• master

This change applies to Uyuni documentation only.

No backport is required.

Links

• This PR tracks issue Podman setup should use version instead of latest tags uyuni#10708
• Related development PR: N/A

Additional notes

This is a documentation-only change. No changelog entry is required.

[nodeg]

Small nitpick.

[pks2906]

Thanks for the suggestion! I've updated the version to a more recent one.

[cbosdo]

I forgot to select the Request changes option earlier. Document the examples with mgradm upgrade podman --tag would be way more useful.

[pks2906]

I've updated the example to include a concrete version instead of a placeholder.

[cbosdo]

It looks better now. Thanks

[pks2906]

Thanks for the review and guidance throughout!

[0rnela]

@cbosdo once this is ready for merge, could you please tag me here? Thanks.

[cbosdo]

For Uyuni, the images for older versions are in a separate path (See them in https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3D%5Esystemsmanagement%3AUyuni%3ASnapshots+container%3D.*).

Before submitting such a documentation it would be nice of you to try it out… You need to pass the *-image parameters to wanted the snapshot path. There, the tag can be either latest or the version tag.

[pks2906]

Thanks for the feedback!

I see the issue with snapshot repositories and the image path. I’ll test the commands locally with the correct parameters and update the documentation accordingly

[cbosdo]

Same for the proxy: this doesn't work with Uyuni and its snapshot repositories.

[pks2906]

Thanks for the feedback!

I’ve updated the documentation to distinguish between stable releases and snapshot repositories clearly, and added examples using the --image parameter for snapshots.

I also tried running the commands locally, but it seems they require a full Uyuni provisioning setup (mgradm is not available in my current environment). Please let me know if you’d like me to validate this further with a proper setup. I'd be happy to explore that next.

[cbosdo]

I’ve updated the documentation to distinguish between stable releases and snapshot repositories clearly, and added examples using the --image parameter for snapshots.

I also tried running the commands locally, but it seems they require a full Uyuni provisioning setup (mgradm is not available in my current environment). Please let me know if you’d like me to validate this further with a proper setup. I'd be happy to explore that next.

To test this, you will need to install mgradm and Uyuni from the snapshot repos. You can install from https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/2026.01/ and then upgrade to https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/2026.03/ . Those repos contain mgradm fixed for those versions too.

[pks2906]

Thanks a lot for the detailed guidance!

This is really helpful. I’ll set up Uyuni using the snapshot repositories you shared and validate the commands in a proper environment.

I’ll update here once I’ve tested it.

[pks2906]

Thanks again for the detailed guidance! @cbosdo

I tested everything inside an openSUSE VM environment (openSUSE Leap) to validate the commands.

Here’s what I tried:

• Used the snapshot repository URLs:

https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/2026.01/
and also:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/2026.01/openSUSE_Leap_15.5/

• While adding the repository using sudo zypper ar, I initially got:

“If only one argument is used, it must be a URI pointing to a .repo file.”
Then retried with an alias.

• After running zypper refresh, I consistently got:
  “Valid metadata not found at specified URL”
  “Repository type can’t be determined”

• I also tried downloading mgradm from the releases, but the URLs returned 404 responses, so I couldn’t execute the commands.

From this, it seems:

• The snapshot repositories are not directly usable in a standalone openSUSE setup
• Validating these commands requires a fully provisioned Uyuni environment

Would it make sense to mention this requirement in the documentation?

Happy to refine the documentation further based on your suggestions.

I’ve attached a screenshot of the VM output for reference.