-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hostPath does not work on containerd on Windows #95547
Comments
@andyzhangx: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm guessing this is the issue. Can you share what mounts you put in the pod spec? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
I am able to deploy a host path pod: https://raw.githubusercontent.com/jsturtevant/windows-k8s-playground/master/deployments/volumes/hostvolume.yaml
Going to close, if you can provide a reproduction please reopen. /close |
@jsturtevant: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
now the following mountPath behavior changed from docker to containerd on Windows:
mount as a D drive
mount as question is how can I mount as a new drive with containerd on Windows? is this a regression? |
That does seem like a regression or bug. The mount path is supposed to be absolute, so I feel like containerd has probably done the wrong thing here. If it really wanted to mount everything under Probably needs to be a new bug report though, perhaps even against containerd, assuming the value came to it via CRI correctly. |
This is tracked via containerd/containerd#6589. |
What happened:
hostPath does not work on containerd on Windows
I tried hostpath example with server:2004 on containerd on Windows and seeing this issue, it works well on docker Windows:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):/kind bug
/priority important-soon
/sig storage
The text was updated successfully, but these errors were encountered: