# Init container unable to connect due to network unavailable **URL:** \ **Category:** Linkerd General Discussion\ **Tags:** proxy, configuration\ **Created:** [October 27, 2023, 9:08pm UTC](https://linkerd.buoyant.io/t/init-container-unable-to-connect-due-to-network-unavailable/304 "2023-10-27T21:08:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![djaramil](https://avatars.discourse-cdn.com/v4/letter/d/a9adbd/32.png) [@djaramil](https://linkerd.buoyant.io/u/djaramil)\ **Post date:** [October 27, 2023, 9:08pm UTC](https://linkerd.buoyant.io/t/init-container-unable-to-connect-due-to-network-unavailable/304/1 "2023-10-27T21:08:49Z")
We use vault in our environment and when we enable linkerd cni, the vault init container is unable to connect because the network is unavailable inside the pod. If we use linkerd without linkerd-cni, the vault container is able to connect just fine. We have tried it on the latest version of linkerd. There is a vault agent that is injecting a vault init container and it is trying to connect to external vault server. ---
**Author:** ![olix0r](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/olix0r/32/133_2.png) [@olix0r](https://linkerd.buoyant.io/u/olix0r)\ **Post date:** [October 27, 2023, 9:17pm UTC](https://linkerd.buoyant.io/t/init-container-unable-to-connect-due-to-network-unavailable/304/2 "2023-10-27T21:17:15Z")
Right. If the CNI sets up iptables before the vault initcontainer runs, there’s no proxy to manage those connections so they can’t succeed. There’s an [open PR](https://github.com/linkerd/linkerd2/pull/11465) to support the new Kubernetes sidecar containers, which will support running the proxy before other initcontainers (like vault). This will fix your problem once it’s merged (if your cluster administrator has enabled sidecar container support). Alternatively, there are some workarounds listed [here](https://linkerd.io/2.14/features/cni/#allowing-initcontainer-networking). Hope this helps!