garden health check failing about garden-runc-release HOT 6 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/156030218

The labels on this github issue will be updated when the story is started.

from garden-runc-release.

Hi @aminjam, are you using cf-release to deploy this? And is there a particular reason you're using diego-release 2.0.0?

The release notes for cf-release v287 specify diego-release v1.34.0 and garden-runc-release v1.11.1. It looks like you might just be using incompatible versions of components.

from garden-runc-release.

@teddyking , That mistake from my side. I am using CF-Deployment(v1.19.0).

from garden-runc-release.

Hi @AmitRoushan - this seems like it would have to be an issue higher up than garden: it's complaining that /home/vcap is inaccessible, which would presumably only happen if the rootfs had incorrect permissions. What stemcell version are you using? Does the error still occur after a bosh recreate?

from garden-runc-release.

@julz , We majorly use saltstack for our deployment. So we have ported bosh script to salt script. Also we are maintaining 'paas' user in deployment VM for deployment instead 'vcap' user. But we still maintain 'vcap' user inside container. Following are permission for different directory in rootfs:

drwxr-x--- 21 root root 4096 Mar 15 06:53 ./
drwxr-x---  3 root root 4096 Mar 12 17:24 ../
lrwxrwxrwx  1 root root   14 Feb 21 20:43 app -> /home/vcap/app
drwxr-xr-x  2 root root 4096 Feb 21 20:38 bin/
drwxr-xr-x  2 root root 4096 Apr 11  2014 boot/
drwxr-xr-x  4 root root 4096 Feb 21 20:43 dev/
-rwxr-xr-x  1 root root    0 Feb 21 20:43 .dockerenv*
drwxr-xr-x 81 root root 4096 Feb 21 20:43 etc/
drwxr-xr-x  3 root root 4096 Feb 21 20:43 home/
drwxr-xr-x 13 root root 4096 Feb 21 20:38 lib/
drwxr-xr-x  2 root root 4096 Jan 24 01:02 lib64/
drwxr-xr-x  2 root root 4096 Jan 24 01:00 media/
drwxr-xr-x  2 root root 4096 Apr 11  2014 mnt/
drwxr-xr-x  2 root root 4096 Jan 24 01:00 opt/
drwxr-xr-x  2 root root 4096 Apr 11  2014 proc/
drwx------  3 root root 4096 Feb 21 20:43 root/
drwxr-xr-x  8 root root 4096 Jan 26 02:22 run/
drwxr-xr-x  2 root root 4096 Feb 21 20:38 sbin/
drwxr-xr-x  2 root root 4096 Jan 24 01:00 srv/
drwxr-xr-x  2 root root 4096 Mar 13  2014 sys/
drwxrwxrwx  2 root root 4096 Mar 15 06:53 tmp/
drwxr-xr-x 10 root root 4096 Jan 24 01:00 usr/
drwxr-xr-x 12 root root 4096 Feb 21 20:43 var/

Thank you!!!

from garden-runc-release.

Hi @AmitRoushan -

I'm afraid it's quite difficult for us to support non-bosh deployments. In this case I suspect what's happened is in recent versions of garden we expect the rootfs to be provided as a tar file rather than a directory.

You can see the changes that were made in cf-deployment for that change here -- in particular see that the preloaded_rootfses property in Diego changed from cflinuxfs2:/var/vcap/packages/cflinuxfs2/rootfs to cflinuxfs2:/var/vcap/packages/cflinuxfs2/rootfs.tar. A similar change was made in the diego-release manifest generation scripts, although those are now deprecated in favour of cf-deployment.

You will need to modify your salt stack scripts along similar lines to the cf-deployment manifest changes above to use recent versions of garden.

Thanks!

from garden-runc-release.