Description

now the following mountPath behavior changed from docker to containerd on Windows:

          volumeMounts:
          - mountPath: 'D:'
            name: azure

• docker on Windows

mount as a D drive

• containerd on Windows

mount as c:\D\ folder

question is how can I mount as a new drive with containerd on Windows? is this a regression?

Steps to reproduce the issue

1. n/a

Describe the results you received and expected

I could still mount hostPath as a new drive with containerd on Windows

What version of containerd are you using?

containerd://1.5.5+azure

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

n/a