You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/02/06 07:04:48 UTC
[GitHub] sven-lange-last commented on issue #4244: Error when deploying:
Failed to initialize reactive invoker
sven-lange-last commented on issue #4244: Error when deploying: Failed to initialize reactive invoker
URL: https://github.com/apache/incubator-openwhisk/issues/4244#issuecomment-460921382
You are running OpenWhisk on Kubernetes and try to use the Docker variant with `whisk.core.containerpool.docker.DockerContainerFactoryProvider`.
Are you sure that your Kubernetes cluster is using Docker under the covers to manage its pods? If there is no Docker daemon running on your cluster's worker nodes, this option won't work.
If you are sure Docker is running, you need to mount the Docker daemon socket into the invoker pod such that the invoker can access it. You likely need these volumes:
```
volumes:
- name: cgroup
hostPath:
path: "/sys/fs/cgroup"
- name: runc
hostPath:
path: "/run/runc"
- name: dockerrootdir
hostPath:
path: "/var/lib/docker/containers"
- name: dockersock
hostPath:
path: "/var/run/docker.sock"
- name: apparmor
hostPath:
path: "/usr/lib/x86_64-linux-gnu/libapparmor.so.1"
```
If there are problems accessing the docker socket or some of the directories, think about running the invoker as a privileged pod.
If no Docker is running under the covers, you have to use the Kubernetes container factory - see https://github.com/apache/incubator-openwhisk-deploy-kube/blob/master/docs/configurationChoices.md#invoker-container-factory.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services