kubernetes/eksdemo - [master鈼廬 禄 k logs -f deployment/cluster-autoscaler-aws-cluster-autoscaler
container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/etc/ssl/certs/ca-certificates.crt\\\" to rootfs \\\"/var/lib/docker/overlay2/695be5c469b0e51f5c9c0780cb296d5660bd86ee81eb02f716d581070ef1fe97/merged\\\" at \\\"/var/lib/docker/overlay2/695be5c469b0e51f5c9c0780cb296d5660bd86ee81eb02f716d581070ef1fe97/merged/etc/ssl/certs/ca-certificates.crt\\\" caused \\\"not a directory\\\"\""
Should be fixed by #9024
/assign @linki
I'm hitting this problem as well; I'm running on EKS using the EKS optimized AMI (Amazon Linux 2)
we're hitting too
@linki is there anything I can do to help get this through ?
@linki ?
Hitting this problem as well.
Me too!
Setting sslCertPath: /etc/kubernetes/pki/ca.crt on EKS resolved this for me
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
This issue is being automatically closed due to inactivity.
For me, the path on the host was incorrect.
sslCertHostPath: /etc/kubernetes/pki/ca.crt
As of version 3.2.0 this is still a problem. The workaround described by @darrylb-github fixes it.
Most helpful comment
Setting
sslCertPath: /etc/kubernetes/pki/ca.crton EKS resolved this for me