MCC Container detected as running, waiting for MCC to return ready status code

We are experiencing an issue when preparing a new Microsoft Connected Cache (MCC) server. During the final stage of the setup, the process hangs indefinitely on:

“MCC Container detected as running, waiting for MCC to return ready status code.”

When checking the container logs, we see the following errors:

Code

Starting module MCC...
Starting new listener for module MCC
Starting workload API...
Workload API stopped
container runtime error
Caused by:
HTTP 500 Internal Server Error: failed to create task for container:
failed to create shim task:
OCI runtime create failed:
runc create failed:
unable to start container process:
error during container init:
error mounting "tmpfs" to rootfs at "/run/mcc":
invalid argument

Our environment:

• Hyper‑V host with nested virtualization enabled

Guest OS: Windows Server 2022 (also tested with 2025)

WSL installed

Hyper‑V and container features enabled

Local runtime account configured

Dedicated cache drive (260 GB)

Same procedure worked without issues until approximately two weeks ago

We would like to know:

Has anything changed recently in the MCC runtime, MSIX installer, or container runtime that could affect tmpfs mounting?

Is this a known issue with Windows Server 2022/2025 or nested virtualization?

Are there updated requirements for running MCC inside a Hyper‑V VM?

We can provide full logs (docker logs, MCC setup logs, WSL diagnostics) if needed.We are experiencing an issue when preparing a new Microsoft Connected Cache (MCC) server.

During the final stage of the setup, the process hangs indefinitely on: