Closed cmoulliard closed 1 year ago
Builder.toml has changed since last time https://github.com/paketo-community/ubi-nodejs-extension/blob/main/README.md
use for the stack
[stack]
id = "io.buildpacks.stacks.ubi8"
build-image = "paketocommunity/build-ubi-base"
run-image = "paketocommunity/run-ubi-base"
and for the lifecycle
[lifecycle]
version = "0.17.0-pre.2"
also the pack version has to be v0.30.0-pre2
or later
Also the build of the app fails with the v0.30.0-rc1 despite it is the latest. I think you have to use the v0.30.0-pre2
.
use for the stack
So you suggest that I change within the builder.toml file
id = "ubi8-paketo"
build-image = "quay.io/midawson/ubi8-paketo-build"
run-image = "quay.io/midawson/ubi8-paketo-run"
to
[stack]
id = "io.buildpacks.stacks.ubi8"
build-image = "paketocommunity/build-ubi-base"
run-image = "paketocommunity/run-ubi-base"
@pacostas
version = "0.17.0-pre.2"
Lifecycle 0.17.0 is out since yesterday @pacostas
Job is failing https://github.com/redhat-buildpacks/testing/actions/runs/5808895386/job/15746619582 when I configure the project as you suggested @pacostas
===> ANALYZING
Running the 'analyzer' on OS 'linux' with:
Container Settings:
Args: '/cnb/lifecycle/analyzer -log-level debug -daemon -stack /layers/stack.toml -run-image paketocommunity/run-ubi-base -launch-cache /launch-cache container-registry.local:5000/nodejs-pack-test:1.0'
System Envs: 'CNB_USER_ID=1001 CNB_GROUP_ID=1000 CNB_PLATFORM_API=0.12'
Image: 'buildpacksio/lifecycle:0.17.0'
User: 'root'
Labels: 'map[author:pack]'
Host Settings:
Binds: '/var/run/docker.sock:/var/run/docker.sock pack-cache-nodejs-pack-test_1.0-811fea5a[297](https://github.com/redhat-buildpacks/testing/actions/runs/5808895386/job/15746619582#step:5:298)4.launch:/launch-cache pack-layers-lhmyunrmen:/layers pack-app-fkbjctmgbg:/workspace'
Network Mode: 'host'
[analyzer] flag provided but not defined: -stack
[analyzer] Usage of lifecycle:
[analyzer] -analyzed string
[analyzer] path to analyzed.toml (default "<layers>/analyzed.toml")
[analyzer] -cache-image string
[analyzer] cache image tag name
[analyzer] -daemon
[analyzer] export to docker daemon
[analyzer] -gid int
[analyzer] GID of user's group in the stack's build and run images (default 1000)
[analyzer] -launch-cache string
[analyzer] path to launch cache directory
[analyzer] -layers string
[analyzer] path to layers directory (default "/layers")
[analyzer] -layout
[analyzer] export to OCI layout format on disk
[analyzer] -layout-dir string
[analyzer] path to output directory for images in OCI layout format
[analyzer] -log-level string
[analyzer] logging level (default "info")
[analyzer] -no-color
[analyzer] disable color output
[analyzer] -previous-image string
[analyzer] reference to previous image
[analyzer] -run string
[analyzer] path to run.toml (default "/cnb/run.toml")
[analyzer] -run-image string
[analyzer] reference to run image
[analyzer] -skip-layers
[analyzer] do not provide layer metadata to buildpacks
[analyzer] -tag value
[analyzer] additional tags
[analyzer] -uid int
[analyzer] UID of user in the stack's build and run images (default 1001)
[analyzer] -version
[analyzer] show version
ERROR: failed to build: executing lifecycle: failed with status code: 2
Error: Process completed with exit code 1.
can you try once more, by changing the lifecycle to
[lifecycle]
version = "0.17.0-pre.2"
on the builder.toml with existing configuration ?
version = "0.17.0-pre.2"
Why ? @pacostas
Interesting: job is working https://github.com/redhat-buildpacks/testing/actions/runs/5810014997/job/15750039495?pr=29 using lifecycle 0.17.0-pre.2
@pacostas
version = "0.17.0-pre.2"
Why ? @pacostas
I dont have enough context about that, but this is temporarily, once the latest version of the lifecycle has the changes for the extension to work, we will unpin it.
Should such extension changes be part of lifecycle 0.17.0 or 0.17.1 or etc ? @pacostas
job succeeded using such parameters: https://github.com/redhat-buildpacks/testing/blob/a54d22b780eb3bffe4fcdfeeac0ac6e293e89d46/.github/workflows/pack_nodejs.yaml
lifecycle 0.17.0 pack client: v0.30.0-rc1
[stack] id = "io.buildpacks.stacks.ubi8" build-image = "paketocommunity/build-ubi-base" run-image = "paketocommunity/run-ubi-base"
@pacostas
Yes they should be, but this is something we are working on ATM.
We are getting an ... old issue as
[detector] failed to satisfy "node" dependency version constraint "16": no compatible versions on "ubi8-paketo" stack. Supported versions are: []
See job: https://github.com/redhat-buildpacks/testing/actions/runs/5807158874/job/15741467352
@mhdawson