0

我正在尝试安装 Kubernetes。

配置细节：

控制器

  • 操作系统：CoreOS alpha (1339.0.0) 的容器 Linux
  • 局域网IP：192.168.1.2

  • FQDN：coreos-2.tux-in.com

  • 用于安装的环境变量：

    export MASTER_FQDN=coreos-2.tux-in.com
export MASTER_IP=192.168.1.2
export WORKER_IP=192.168.1.3
export WORKER_FQDN=coreos-3.tux-in.com
export ETCD_ENDPOINTS=http://127.0.0.1:4001
export ADVERTISE_IP=192.168.1.2
export K8S_VER=v1.5.4_coreos.0
export HYPERKUBE_IMAGE_REPO=quay.io/coreos/hyperkube
export POD_NETWORK=10.2.0.0/16
export SERVICE_IP_RANGE=10.3.0.0/24
export K8S_SERVICE_IP=10.3.0.1
export DNS_SERVICE_IP=10.3.0.10
export USE_CALICO=true
export CONTAINER_RUNTIME=rkt
export EMAIL="kfirufk@gmail.com"
export uuid_file="/var/run/kubelet-pod.uuid"

工人

  • 操作系统：CoreOS alpha (1339.0.0) 的容器 Linux
  • 局域网IP：192.168.1.3

  • FQDN：coreos-3.tux-in.com

  • 用于安装的环境变量

    export ETCD_ENDPOINTS=http://127.0.0.1:4001
export CONTROLLER_ENDPOINT=https://coreos-2.tux-in.com
export ADVERTISE_IP=192.168.1.3
export K8S_VER=v1.5.4_coreos.0
export HYPERKUBE_IMAGE_REPO=quay.io/coreos/hyperkube
export POD_NETWORK=10.2.0.0/16
export DNS_SERVICE_IP=10.3.0.10
export USE_CALICO=true
export CONTAINER_RUNTIME=rkt
export EMAIL="kfirufk@gmail.com"
export uuid_file="/var/run/kubelet-pod.uuid"
export  CALICO_OPTS="--volume cni-bin,kind=host,source=/opt/cni/bin \
            --mount volume=cni-bin,target=/opt/cni/bin"

我使用我的 forkcoreos-kubernetes来安装控制器和工作程序（https://github.com/kfirufk/coreos-kubernetes）。

控制器节点运行良好，但工作节点permission denied在尝试在 kubernetes 告诉它执行的每个图像上运行 rkt 时抱怨。

例如：

Mar 11 21:34:58 coreos-3.tux-in.com kubelet-wrapper[10203]: E0311 21:34:58.654536   10203 pod_workers.go:184] Error syncing pod ac3615637dcb614ace172dc5c5dd85f3, skipping: failed to SyncPod: failed to run [prepare --quiet --pod-manifest /tmp/manifest-kube-proxy-192.168.1.3-986457484 --stage1-name=coreos.com/rkt/stage1-fly]: fork/exec /usr/bin/rkt: permission denied

有任何想法吗 ？

4

1 回答 1

0

这是一个简单的问题。

我指向kubelet.service运行 rkt，/opt/bin/host-rkt其中包含：

#!/bin/sh
# This is bind mounted into the kubelet rootfs and all rkt shell-outs go
# through this rkt wrapper. It essentially enters the host mount namespace
# (which it is already in) only for the purpose of breaking out of the chroot
# before calling rkt. It makes things like rkt gc work and avoids bind mounting
# in certain rkt filesystem dependancies into the kubelet rootfs. This can
# eventually be obviated when the write-api stuff gets upstream and rkt gc is
# through the api-server. Related issue:
# https://github.com/coreos/rkt/issues/2878
exec nsenter -m -u -i -n -p -t 1 -- /usr/bin/rkt "$@"

而且它没有可执行权限。就是这样..一个简单的chmod +x /opt/bin/host-rkt解决它:)

于 2017-03-11T21:57:19.483 回答