-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
docker in docker not working after upgrading nodes to 1.14 #334
Comments
Hi yaramada, did you updated an existing old cluster to 1.14? Reference: https://docs.aws.amazon.com/eks/latest/userguide/pod-security-policy.html |
we updated existing clusters to 1.14 and after adding this it started working back again. |
I would rather use Kaniko or something similar on Kubernetes instead of Docker for building OCI Images, we use Kaniko in our CI on Kubernetes happily, without any issues: https://banzaicloud.com/blog/unprivileged-builds/ |
@yrsurya |
What happened:
We use jenkins to build image and push to ECR which uses underlying docker so we mount /var/run/docker.sock in Kubernetes plugin configuration in jenkins. It works fine till now but broke after upgrading needs to 1.14 which affects our CI builds.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
):"eks.1"aws eks describe-cluster --name <name> --query cluster.version
):"1.14"amazon-eks-node-1.14-v20190906 (ami-08739803f18dcc019)
uname -a
):Linux 4.14.138-114.102.amzn2.x86_64 Template is missing source_ami_id in the variables section #1 SMP Thu Aug 15 15:29:58 UTC 2019 x86_64 x86_64 x86_64 GNU/Linuxcat /etc/eks/release
on a node):NAME="Amazon Linux"VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"
The text was updated successfully, but these errors were encountered: