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.

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

kubeadm & weave: No networks found in /etc/cni/net.d #147

Open
discostur opened this issue Nov 20, 2017 · 5 comments
Open

kubeadm & weave: No networks found in /etc/cni/net.d #147

discostur opened this issue Nov 20, 2017 · 5 comments
Assignees
Labels

Comments

@discostur
Copy link

discostur commented Nov 20, 2017

Hi,

i'm trying to setup k8s 1.8.x on fedora host 27 with the kubeadm system container:

setenforce 0
atomic install --system --system-package=no --name kubelet jasonbrooks/kubeadm
systemctl daemon-reload
systemd-tmpfiles --create /etc/tmpfiles.d/kubelet.conf
systemctl enable kubelet
kubeadm init --skip-preflight-checks

export kubever=$(kubectl version | base64 | tr -d '\n')
kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$kubever"

After that i'm seeing the following error messages:

Nov 20 11:47:43 fedora-atomic-host runc[3522]: W1120 10:47:43.656415    3532 cni.go:196] Unable to update cni config: No networks found in /etc/cni/net.d
Nov 20 11:47:43 fedora-atomic-host runc[3522]: E1120 10:47:43.656627    3532 kubelet.go:2095] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Nov 20 11:47:48 fedora-atomic-host runc[3522]: W1120 10:47:48.658418    3532 cni.go:196] Unable to update cni config: No networks found in /etc/cni/net.d
Nov 20 11:47:48 fedora-atomic-host runc[3522]: E1120 10:47:48.658588    3532 kubelet.go:2095] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Nov 20 11:47:48 fedora-atomic-host dockerd-current[1294]: 2017-11-20 10:47:48.904677 W | etcdserver: apply entries took too long [10.1646ms for 1 entries]
Nov 20 11:47:48 fedora-atomic-host dockerd-current[1294]: 2017-11-20 10:47:48.904714 W | etcdserver: avoid queries with large range/delete range! 

Kubectl shows me that the "po/kube-controller-manager-fedora-atomic-host" is pending in the "ContainerCreating" state.

Does anybody have an idea whats wrong?

@ashcrow
Copy link
Collaborator

ashcrow commented Nov 20, 2017

/cc @jasonbrooks

@discostur
Copy link
Author

@jasonbrooks Any news on this?

@jasonbrooks
Copy link
Collaborator

@discostur I've been trying to figure this out -- perhaps something has changed w/ 1.8

@jasonbrooks
Copy link
Collaborator

If I change the FROM line to registry.fedoraproject.org/fedora:27 I get a 1.7.x kube, and the container works.

It looks like for 1.8.x we might need kubernetes/kubernetes#55955

@jasonbrooks
Copy link
Collaborator

This container works on regular fedora, where /usr/libexec/kubernetes is writable. Kubeadm has this hardcoded, the PR linked above is supposed to fix that, and make it configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants