Relevant area(s)
Windows
Brief description of your issue
Applications running inside the MXC sandbox are unable to successfully apply or enforce policies when operating against content located on a Windows Dev Drive volume.
This impacts scenarios where MXC policy enforcement, filesystem governance, isolation rules, or related configuration mechanisms are expected to function on repositories, toolchains, or workloads hosted on Dev Drives.
Steps to reproduce
- Create or mount a Windows Dev Drive volume
- Place application/workload/repository on the Dev Drive
- Launch application inside MXC sandbox
- Attempt to apply or enforce MXC policies
- Observe policy application failure or inconsistent behavior
Expected behavior
MXC sandboxed applications should be able to:
- Apply policies consistently across Dev Drive volumes
- Enforce sandbox restrictions correctly on Dev Drive-backed content
Actual behavior
- Policy application fails for paths hosted on a Dev Drive
- Operations succeed on standard NTFS volumes but fail on Dev Drive volumes
Relevant area(s)
Windows
Brief description of your issue
Applications running inside the MXC sandbox are unable to successfully apply or enforce policies when operating against content located on a Windows Dev Drive volume.
This impacts scenarios where MXC policy enforcement, filesystem governance, isolation rules, or related configuration mechanisms are expected to function on repositories, toolchains, or workloads hosted on Dev Drives.
Steps to reproduce
Expected behavior
MXC sandboxed applications should be able to:
Actual behavior