Unable to run customized Docker app after upgrade

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Symptoms:

After upgrading Elastic Runtime, you may see that a customized Docker app fails to start. On closer inspection you can see that files which have been removed from the Docker image still appear to exist.

In the example below, a Docker file was used to build and remove the file 'welcome.conf', however that is still present in the image when run on Pivotal Cloud Foundry. Further more, the permissions on this file are invalid.

[root@cake conf.d]# ls -la
ls: cannot access 'welcome.conf': No such file or directory

total 16
drwxr-xr-x 1 root root   25 Jun  6 09:53 .
drwxr-xr-x 1 root root   19 Jun  6 09:53 ..
-rw-r--r-- 1 root root  366 May  1 08:54 README
-rw-r--r-- 1 root root   21 Jun  6  2018 ServerName.conf
-rw-r--r-- 1 root root 2893 May  1 08:54 autoindex.conf
-rw-r--r-- 1 root root 1252 May  1 08:51 userdir.conf
?????????? ? ?    ?       ?            ? welcome.conf

 

Environment

Cause

There is a known bug (https://github.com/cloudfoundry/garden-runc-release/issues/77) in garden-runc v1.13.1. If you have a Docker image which deletes some files during its build then these files may not get fully cleaned up and can cause issues with your container e.g. unable to run an app. The xfs store did not have ftype=1 set due to an old version of xfsprogs in the stemcell, causing issues with deleted files in application containers created from Docker images.

Resolution

The fix for the issue is update to garden-runc release v1.13.3
This is currently being added to the next release of ERT 1.12.x (should be 1.12.25),  PAS 2.0.x (should be 2.0.16) and PAS 2.1.x (should be 2.1.7).