kubernetes: local cluster up fails on fedora 26
What happened: the kube-dns pod is getting EPERM’d because of https://github.com/kubernetes/kubernetes/blob/dc0013a506d50c54d5a5833e92d82fce61301c2e/cluster/addons/dns/kube-dns/kube-dns.yaml.in#L156 introduced in https://github.com/kubernetes/kubernetes/pull/82347
I have reproduced this with both docker version 1.13.1 and upstream CRI-O (v1.16.0-dev). Both with kubernetes master.
What you expected to happen:
the cluster to come up
How to reproduce it (as minimally and precisely as possible):
run hack/local-up-cluster.sh
on fedora 26
Environment:
- Kubernetes version (use
kubectl version
):
Client Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.0-alpha.0.1998+8a123346838d4b-dirty", GitCommit:"8a123346838d4b96b68835aebf45a4334867113c", GitTreeState:"dirty", BuildDate:"2019-10-02T15:37:01Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.0-alpha.0.1998+8a123346838d4b-dirty", GitCommit:"8a123346838d4b96b68835aebf45a4334867113c", GitTreeState:"dirty", BuildDate:"2019-10-02T15:37:01Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
- Cloud provider or hardware configuration: AWS
- OS (e.g:
cat /etc/os-release
):
NAME=Fedora
VERSION="26 (Cloud Edition)"
ID=fedora
VERSION_ID=26
PRETTY_NAME="Fedora 26 (Cloud Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:26"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=26
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=26
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
VARIANT="Cloud Edition"
VARIANT_ID=cloud
- Kernel (e.g.
uname -a
):
Linux ip-172-18-18-7.ec2.internal 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (16 by maintainers)
@bowei I’m trying f30 now, I’ll report back my findings.
@pjbgf thanks for looking into it. I’m a maintainer of CRI-O, and its currently blocking our CI. I haven’t reproduced the issue outside of CI, yet, so it may be our machine configuration. I’m not convinced it’s a problem in CRI-O, because I also reproduced with docker. I am going to try to upgrade fedora versions and see if that does it.
Also, if you continue having trouble building CRI-O master, we’d love to hear about it 😄