Docker file permission issue after upgrading PCF about garden-runc-release HOT 4 CLOSED

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

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

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

from garden-runc-release.

Hi @cah-andrewfitzgerald, thanks for submitting this issue.
Could you confirm that this is the Dockerfile used to build the image: https://hub.docker.com/r/prom/prometheus/~/dockerfile/
Could you also let me know which version you upgraded from.
Thanks!

from garden-runc-release.

Confirming that is the correct Dockerfile.

@cah-jeremykuhn, do you happen to know the previous version?

from garden-runc-release.

Hey @cah-andrewfitzgerald. We have found that this failure was caused by the combination of this security fix in the image, and the way that our rootfs provider (GrootFS) handled volumes in Garden-Runc-Release 1.12.1.

If you don't want to bump your PCF, you could create a new docker image based on the official one and just remove the VOLUME directive. It would then run on Garden-Runc-Release 1.12.1.

In versions 1.13.1 (PCF 1.12.22) and later, GrootFS will lay down volumes as prescribed in the image (in this case chowned to the user nobody), so the prometheus image should work.
GRR 1.13.1 does have some other known issues, but volumes is not one of them :) .

from garden-runc-release.