Skip to content
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.

Sign up for GitHub

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

Jump to bottom

automountServiceAccountToken not working on Windows #446

Open
xinfengliu opened this issue Mar 21, 2025 · 0 comments · May be fixed by #448
Open

automountServiceAccountToken not working on Windows #446

xinfengliu opened this issue Mar 21, 2025 · 0 comments · May be fixed by #448

Comments

@xinfengliu
Copy link
Contributor

The pod fails to start when automountServiceAccountToken is set to true.

The mount spec passed by kubelet should be corrected for Windows:

Warning Failed 23m (x9 over 29m) kubelet Error: Error response from daemon: invalid volume specification: 'C:\k\pods\ecdaca47-94a0-4b8a-9e8e-086b68769fe7\volumes\kubernetes.io~projected\kube-api-access-zbphk:/var/run/secrets/kubernetes.io/serviceaccount:ro'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Correct Windows bind mount path xinfengliu/cri-dockerd
1 participant
@xinfengliu