Containers failing to create in Windows node of Kubernetes

General Discussions Windows
1

Hi Team,

I am having a heterogeneous(Linux + windows nodes) Kubernetes cluster with version 1.15.3. The windows node was added to the cluster. When I am trying to spin up a pod in windows node, it is stuck in ContainerCreating status. When I describe the pod I am seeing the below error.
I manually added /run/flannel/subnet.env in master node, as I received /run/flannel/subnet.env: no such file or directory error.

Error: NetworkPlugin cni failed to set up pod “hello_default” network: /run/flannel/subnet.env is missing FLANNEL_NETWORK

Warning FailedCreatePodSandBox 70s kubelet, frsdocker5 Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container “ac6f61f6c260cc1955b79c4a70f5e3e9f501c807fd3d739946aeedeed8eee15b” network for pod “hello”: NetworkPlugin cni failed to set up pod “hello_default” network: /run/flannel/subnet.env is missing FLANNEL_NETWORK
Warning FailedCreatePodSandBox 69s kubelet, frsdocker5 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create a sandbox for pod “hello”: Error response from daemon: Conflict. The container name “/k8s_POD_hello_default_6b6c5f9c-470a-4351-b65f-200555f92a98_0” is already in use by container “ac6f61f6c260cc1955b79c4a70f5e3e9f501c807fd3d739946aeedeed8eee15b”. You have to remove (or rename) that container to be able to reuse that name.
Warning FailedCreatePodSandBox 57s kubelet, frsdocker5 Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container “dbc4bc1066d15b2e79aa8627008e998f8ffe3cd06aade8841e3bf7478d62d0fd” network for pod “hello”: NetworkPlugin cni failed to set up pod “hello_default” network: /run/flannel/subnet.env is missing FLANNEL_NETWORK
Warning FailedCreatePodSandBox 7s (x5 over 56s) kubelet, frsdocker5 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create a sandbox for pod “hello”: Error response from daemon: Conflict. The container name “/k8s_POD_hello_default_6b6c5f9c-470a-4351-b65f-200555f92a98_0” is already in use by container “dbc4bc1066d15b2e79aa8627008e998f8ffe3cd06aade8841e3bf7478d62d0fd”. You have to remove (or rename) that container to be able to reuse that name.

Can someone please help me to fix this.

Thanks,
Ramesh