v0.27.0: ERROR: failed to create launch cache: permission denied

[robdimsdale]

Summary

When upgrading from pack 0.26.0 to pack 0.27.0 previously-successful builds are now failing with the following error:

[analyzer] ERROR: failed to create launch cache: initializing staging directory '/launch-cache/staging': mkdir /launch-cache/staging: permission denied

Example build failing in CI: https://github.com/paketo-buildpacks/jammy-tiny-stack/pull/18/checks

The buildpacks involved are:

• 'paketo-buildpacks/go-dist' version '1.2.1' (API 0.7)
• 'paketo-community/build-plan' version '0.1.0' (API 0.6)

[edmorley]

We encountered this too, until we upgraded the lifecycle in our builder image from 0.14.0 to 0.14.1.

eg:
https://app.circleci.com/pipelines/github/heroku/buildpacks-jvm/1061/workflows/dd3c6153-ebc2-4ab5-aeb4-589aa5bcda29/jobs/13385

[edmorley]

xref #1417 and buildpacks/lifecycle#847

[natalieparellano]

@jromero should we call this out in the release notes?

[jromero]

At minimum, that sounds reasonable.

@natalieparellano could you provide some context as to what is happening for those that are curious? Also, are there any strategies we can think of to mediate this a bit better?

cc: @dfreilich

[jromero]

After further investigation and consideration, given that this bug is only present in very specific set of conditions and the actual bug resides elsewhere (lifecycle 0.14.0), we don’t believe that there are any changes necessary for pack.

We have updated the release notes to call out the known issue (the incompatibility with lifecycle 0.14.0) and possible workarounds.

As builders get updated with the latest patched lifecycle version this issue should naturally become less relevant.