Microsoft Connected Cache (ISP) - Supported Moby Engine Versions for RHEL 9

Question

We are evaluating Microsoft Connected Cache (ISP deployment) on RHEL 9.

The MCC documentation indicates that RHEL 8.x and 9.x are supported and that the default container runtime (Podman) should be replaced with Moby.

Before building our production environment, we would like clarification on the supported Moby Engine versions.

Questions:

What Moby Engine version is currently supported for MCC deployments on RHEL 9?

Does MCC require a specific Moby version, or is there a supported version range?

Is the Moby version installed and managed by the MCC provisioning package, or is it expected to be maintained by the operator?

How are security updates and Moby CVEs handled in supported MCC deployments?

Are there any known compatibility restrictions with hardened RHEL 9 builds (SELinux Enforcing, CIS/STIG baselines, etc.)?

We would appreciate guidance from the MCC product team or operators who have deployed MCC on RHEL.

Answer 1

The available documentation in context does not specify supported Moby (moby-engine/moby-cli) versions, version ranges, or RHEL 9 hardening constraints for Microsoft Connected Cache for ISPs. It only states that Azure IoT Edge uses Moby-based Docker components and that these are updated as part of the Connected Cache lifecycle.

From the provided information, the only supported statements are:

• Microsoft Connected Cache is deployed as an Azure IoT Edge module and uses Moby-based Docker components (moby-engine, moby-cli) for container management.
• These Moby components are updated as part of Connected Cache lifecycle operations to maintain compatibility with the Azure IoT Edge infrastructure and the MCC container images.
• Kernel-level and host-level network configurations are also tuned and may be updated as part of lifecycle operations.

The context does not provide:

• A specific supported Moby version or a version range for RHEL 9.
• Whether the operator or MCC is responsible for ongoing Moby package lifecycle management beyond what MCC/IoT Edge updates perform.
• Any documented process for handling Moby-related security updates or CVEs in MCC deployments.
• Any explicit compatibility guidance or restrictions for hardened RHEL 9 builds (SELinux enforcing, CIS/STIG baselines, etc.).

Given the available information, only the general behavior can be stated: MCC (via Azure IoT Edge) installs and updates Moby-based Docker components as part of its lifecycle to stay compatible with MCC container images; no further versioning or hardening guidance is documented in the provided context.

---

References:

• Configure container update frequency for Microsoft Connected Cache for Enterprise and Education
• Microsoft Connected Cache for Enterprise and Education Requirements
• What is Microsoft Connected Cache?
• Verify cache node functionality and monitor health and performance