Help Using Extensions #244
-
|
I am trying to use a Dockerfile extension to add a n OS library to the builder and runner images. I followed the samples to layout the extension locally, enabled experimental support, and ran pack. I have hit a wall that I am struggling to get past. Any ideas what is going on? Pack Command Output |
Beta Was this translation helpful? Give feedback.
Answered by
natalieparellano
Nov 13, 2023
Replies: 2 comments 3 replies
-
|
I'm also having this issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This is "by design" but I don't think we anticipated the poor UX - now that the Paketo builder contains extensions, you can't run the creator, because the creator doesn't support extensions. In the short term, you can get around this by "untrusting" the Paketo builder, which will cause the lifecycle to run in 5 separate containers. You need to do this by re-tagging the builder locally so that it will no longer be "suggested" (see buildpacks/pack#1500) and will therefore be untrusted by default. In the long term, we should probably allow the creator to run and let the lifecycle fail out after detect if the group contains extensions. I can file an issue on the lifecycle. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
@natalieparellano thanks for your reply, it helped a lot. I was able to create a working example of an extensions. I had to turn off the detect script for extensions otherwise lifecycle claimed the extension was unused. I tried following the vim example with the following detect script #!/usr/bin/env bash
set -eo pipefail
# 1. GET ARGS
plan_path=$CNB_BUILD_PLAN_PATH
# 2. DECLARE DEPENDENCIES (OPTIONAL)
cat >> "${plan_path}" <<EOL
# Extension provides this dependency
[[provides]]
name = "audiowaveform"
EOLAny ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I think you need a buildpack to "require" |
Beta Was this translation helpful? Give feedback.
-
|
@natalieparellano Thanks, that worked |
Beta Was this translation helpful? Give feedback.
Answer selected by
a1flecke
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is "by design" but I don't think we anticipated the poor UX - now that the Paketo builder contains extensions, you can't run the creator, because the creator doesn't support extensions.
In the short term, you can get around this by "untrusting" the Paketo builder, which will cause the lifecycle to run in 5 separate containers. You need to do this by re-tagging the builder locally so that it will no longer be "suggested" (see buildpacks/pack#1500) and will therefore be untrusted by default.
In the long term, we should probably allow the creator to run and let the lifecycle fail out after detect if the group contains extensions. I can file an issue on the lifecycle.