fork / exec / usr / bin / rkt：权限被拒绝

Question

我正在尝试安装Kubernetes。

配置详情：

的Controler

• 操作系统：CoreOS alpha的容器Linux（1339.0.0）
• LAN 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的容器Linux（1339.0.0）
• LAN 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"
  

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

控制器节点运行正常，但是当尝试在kubernetes告诉它执行的每个映像上运行rkt时，工作节点会抱怨permission denied。

例如：

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

任何想法？

Answer 1

这是一个简单的问题。

我指出kubelet.service与/opt/bin/host-rkt一起运行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解决了它：）