pack: Regression in v0.30.0-pre3 ?

Summary

Running the smoke test for the ubi-builder-base which uses the ubi-ndoejs-extension that we have been working on works with v0.30.0-pre2 but not with v0.30.0-pre3.

The error seems to be:

           [restorer] ERROR: failed to read builder image: failed to create cache directory: mkdir /kaniko/cache: permission denied
            ERROR: failed to build: executing lifecycle: failed with status code: 1

Reproduction

Steps

checkout this GitHub repo- https://github.com/paketo-community/builder-ubi-base
cd builder-ubi-base
edit scripts/.util/tools.json to change v0.30.0-pre3 to v0.30.0-pre2
run “bash scripts/smoke.sh”

Current behavior

Fails with the error shown above.

Expected behavior

container builds and smoke tests passes

Environment

pack info

<!--- Run `pack report` and copy output here. -->
user1@fedora .bin]$ ./pack report
Pack:
  Version:  0.30.0-pre3+git-cc6b001.build-4846
  OS/Arch:  linux/amd64

Default Lifecycle Version:  0.17.0-rc.3

Supported Platform APIs:  0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12

Config:
  default-builder-image = "[REDACTED]"
  experimental = true
  layout-repo-dir = "/home/user1/.pack/layout-repo"

docker info

About this issue

Original URL
State: closed
Created a year ago
Comments: 18 (8 by maintainers)

Most upvoted comments

@jjbustamante thanks, just back from holidays last week. Will try to test it out early this week.

mhdawson on Aug 14, 2023

@natalieparellano thanks for getting that to work. Just to confirm, the only changes that will be required once we have a version of pack with the newer lifecycle will be the change in nodejs_test.go on line 61 and then those changes in scripts/smoke.sh? If so that is good news and I’ll queue up a PR that we can land once there is a newer pack.

Once I’m back from holiday (I’m out from Aug 7 through 11) I’ll look at how to apply something similar to the integration testing for the extension (versus the builder) which uses occam. My guess is we might need some updates to occam to optionally use a registry to build/run images. @pacostas if you have some cycles before I’m back this might be something you can look at as well.

mhdawson on Aug 3, 2023