lifecycle
lifecycle copied to clipboard
Reference implementation of the Cloud Native Buildpacks lifecycle
### Description AWS ECR does not support the delete image registry API used by pack. See https://github.com/aws/containers-roadmap/issues/1229 When publishing a cache image to an ECR registry, users get the following...
### Description go 1.16 became unsupported when go 1.18 was released. https://github.com/buildpacks/lifecycle/pull/839 upgrades the go version to 1.17, but at some point, we'll want to upgrade to 1.18. ### Proposed...
Before v1.0.0, we should fix the buildpack ID field in the `io.buildpacks.lifecycle.metadata` label: https://github.com/buildpacks/lifecycle/blob/7617cba81b8421a4386188914bd46a8f3a8f8bdd/metadata.go#L105 `key` should be `id` to match all other data structures / serializations that contain a buildpack...
I'm building a Spring Boot application using Gradle. I tried using the builder:base image. It's failing with the following error: ``` Paketo Gradle Buildpack 6.0.1 https://github.com/paketo-buildpacks/gradle Build Configuration: $BP_GRADLE_BUILD_ARGUMENTS --no-daemon...
We currently have a machine in Equinix Metal that is manually provisioned. We should automate its setup. See github.com/buildpacks/ci for how other self-hosted runners are provisioned.
Now, after we moved the release process to Github Actions (see #415), we would like to add a Github Actions workflow for auto-merging `release` branches into `main` ~~after the releases...
This issue have been automatically created from pull request buildpacks/rfcs#166. ### A/C Given for example the following file tree: ``` /layers /config /sbom /launch /buildpack.id bom.cdx.json
[RFC 0076](https://github.com/buildpacks/rfcs/blob/main/text/0076-windows-security-identifiers.md) https://github.com/buildpacks/rfcs/pull/133 * Replace CNB_USER_ID and CNB_GROUP_ID with CNB_USER_SID and CNB_GROUP_SID on windows stack images * Replace `-uid` and `-gid` flags with `-usid` and `-gsid` flags for builds in...
### Summary When the lifecycle does not have the credentials needed to pull the `run-image` it prints a misleading error message claiming that the as-yet-to-be-created app-image has no layers: ```...
Currently, the acceptance tests don't work on Windows. We should fix that! Known issues with analyzer acceptance tests (https://github.com/buildpacks/lifecycle/pull/319): * Can't connect to insecure registry. Because `--network host` does not...