diego-cell pod does not start completely

[dheerajinganti]

I took the latest 2.4.0 release and tried to deploy from scratch. However, diego-cell doesn’t start fully with rep-rep container going into crashloop with below error

k8s version: 1.17.7
node os version: CentOS Linux release 7.8.2003 (Core)

[jandubois]

I think this is a kernel issue; a recent change to garden-runc-release means it now requires Kernel version 4.5 or later:

concourse/concourse#5711 (comment)

I suspect that means you will need to move to CentOS 8 to get kubecf working.

[jandubois]

I suspect that means you will need to move to CentOS 8 to get kubecf working.

Forgot to mention: garden-runc-release is only used by Diego, so if switching to a current Linux kernel is an issue, then maybe you could try switching to Eirini instead.

[dheerajinganti]

Thank you. Yes, I am able to run Eirini with current centos 7.8 version. However strangely, I am unable to pull images from any docker registry. I am able to push apps though with buildpcks. Should I open a new issue for the same?

[jandubois]

I am unable to pull images from any docker registry. [...] Should I open a new issue for the same?

Yes, please!

I can't remember testing docker apps from private repos, but it worked for apps hosted on Docker Hub as long as they used port 8080 to communicate: cloudfoundry/eirini-release#147

[dheerajinganti]

Thank you for the confirmation. This explains why pushing docker images from my private registry is not working with 2.3.0. I am using different port than 8080
For 2.4.0 docker push doesn't work at all. Created an issue #1304 .