# FailedMount kube-api-access when starting windows server core container

**URL:** <https://discuss.kubernetes.io/t/failedmount-kube-api-access-when-starting-windows-server-core-container/18542>\
**Category:** Windows\
**Created:** [December 28, 2021, 7:53pm UTC](https://discuss.kubernetes.io/t/failedmount-kube-api-access-when-starting-windows-server-core-container/18542 "2021-12-28T19:53:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesr](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@jamesr](https://discuss.kubernetes.io/u/jamesr)\
**Post date:** [December 28, 2021, 7:53pm UTC](https://discuss.kubernetes.io/t/failedmount-kube-api-access-when-starting-windows-server-core-container/18542/1 "2021-12-28T19:53:25Z")

</div>

Environment:  
Kubernetes version: v1.23.1  
Cloud being used: bare-metal  
Installation method: kubeadm  
Host OS: Ubuntu 18.04 LTS  
Node OS: Windows Server 2019

I was attempting to start a quick windows server pod to test a couple things using the command

```auto
kube run windows --image=mcr.microsoft.com/windows/servercore:ltsc2019 --restart=Never --command cmd /c "timeout /T 99999" --overrides='{ "spec": { "tolerations" : [{ "key": "build", "operator": "Exists", "effect": "NoSchedule" }], "nodeSelector": { "kubernetes.io/os": "windows" } } }'

```

During startup the pod sits in an error state with the last even being

```auto
Warning FailedMount 6s (x3 over 8s) kubelet MountVolume.SetUp failed for volume "kube-api-access-ng9tk" : object "default"/"kube-root-ca.crt" not registered

```

I haven’t been able to track down an issue with it, and it’s a bit surprising it would have issues with a bare container.  
Any help would be greatly appreciated!