Container Not Working on Windows Factory OS

Hi Utah Maxxn,

Based on what I saw, the container in your Windows Factory OS environment is not starting because the system resources and build you’re using (Dev build 22000.1 with only 2 GB RAM and a 42 GB disk) are below the practical requirements for container initialization. That's the reason why although “Container Support Enabled” is ticked, the container runtime can't come online under these limitations. To resolve this, you need to increase the VM/device resources and ensure you’re on a supported build of Factory OS.

1. To increase system resources, you should:
   • Allocate at least 4 GB RAM (8 GB recommended for stability).
   • Expand the virtual disk to 64 GB or more. Containers need scratch space for images and logs.
2. Update to a newer Factory OS build
   • Use the latest available Factory OS image from Microsoft’s OEM/IoT channel. Build 22000.1 is outdated and has known container issues.
   • Reference: Welcome to Factory OS – Microsoft Learn
3. Verify container service status
   • In Factory Orchestrator, confirm “Container Running ” appears. If it still hangs, check logs under: Code

          C:\ProgramData\DataFactoryOrchestrator\Logs\
     

   • Look for errors related to hcs (Host Compute Service) or insufficient memory.
4. Reset container environment
   • Stop the Factory Orchestrator service.
   • Delete the container state folder (if present): Code

          C:\ProgramData\Microsoft\Windows\Containers
     

   • Restart the service and allow it to re‑initialize.

If you find this information useful to some extent, please accept the answer so that your experience with the issue would help contribute to the whole community. Thank you :)

Vivian

Hi Utah Maxxn,

Has your issue been solved? If it has, don't forget to accept the answer so that your experience with the issue could be spread further to those in need too. If not, is there anything I can help you with? Please let me know. :)

Vivian