Paketo Buildpacks
Replies: 8 comments 31 replies
-
|
Hi @Sunny-001! I think detection is failing because you're using a builder, which has pre-defined buildpack groups, but then you're also defining a buildpack to use. By passing in a single buildpack, you're overriding those groups and ONLY providing a single buildpack to the build. If you want to pass in a custom buildpack, you need to pass in all of the buildpacks in the group. |
Beta Was this translation helpful? Give feedback.
-
|
For example (if your app uses Node Engine, NPM Install, and Node Start) |
Beta Was this translation helpful? Give feedback.
-
|
Separately, you might consider using a dependency mapping type service binding instead to use your own dependency. If you use a dependency mapping for your dependency, then you don't even need to pass in your own buildpack, you can just do something like this, where the binding is a dependency mapping (from the service binding docs): |
Beta Was this translation helpful? Give feedback.
-
|
Hi @sophiewigmore and @dmikusa! |
Beta Was this translation helpful? Give feedback.
-
|
Dependency mappings don't have to point to the local file system they can point anywhere, so it can reference a URL. You can put a user/password into the URL and I think it might use that as HTTP basic credentials. I haven't tried it, but if it doesn't work it should, so you could open an issue against https://github.com/paketo-buildpacks/libpak/issues. I can't speak for buildpacks based on packit, maybe @sophiewigmore knows. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @dmikusa. Putting username/password in the URL works. But those credentials get printed to stdout in plain text at the moment. I have opened a PR to solve this issue: paketo-buildpacks/libpak#312 |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I want to download Node Engine from my private server. What should I do |
Beta Was this translation helpful? Give feedback.
-
|
You can either do what you are doing with your custom buildpack or follow the dependency mapping comment I posted above.
|
Beta Was this translation helpful? Give feedback.
-
|
The information you provided is very useful, thank you very much! |
Beta Was this translation helpful? Give feedback.
-
|
I found some useful information here, maybe I see what you mean, I will try it tomorrow |
Beta Was this translation helpful? Give feedback.
-
|
In regards to dependency mapping, I typically find those work best for local development. It can be tricky to get them into a build system/CI/kpack. They can also be a little tricky to get formatted correctly, which is why I created the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much,I will try tomorrow |
Beta Was this translation helpful? Give feedback.
-
|
@dmikusa First of all, thank you very much for your help, I learned a lot of useful information from your reply and applied it to the build process, and it was very useful. But I ran into a problem when building the vue project. The build command is as follows:
I created the corresponding file according to the instructions, set the environment variable SERVICE_BINDING_ROOT during construction, and mounted the directory /root/npm-bindings/, the directory structure and file contents of /root/npm-bindings/ are as follows：
this configuration does not appear to be in effect, and the following error occurs at build time If I place the.npmrc file directly in the vue project directory, you can clearly see the build speed |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, that's getting out of my area of expertise, @paketo-buildpacks/nodejs-maintainers - any ideas on the above? |
Beta Was this translation helpful? Give feedback.
-
|
@sophiewigmore Can you help me with this question? |
Beta Was this translation helpful? Give feedback.
-
|
Do you see a line that says |
Beta Was this translation helpful? Give feedback.
-
|
the command and build log are as follows, -bash-4.2# pack build ruoyi-ui:2.0.0 \
Paketo CA Certificates Buildpack 3.0.1 Reusing cached layer /layers/paketo-buildpacks_node-engine/node Paketo NPM Install Buildpack 0.6.2 Executing build process ERROR: failed to build: exit status 1 |
Beta Was this translation helpful? Give feedback.
-
|
It looks like you're using a very old version of the buildpacks! For instance, the latest version of the npm-install buildpack is 0.10.8 and you're using 0.6.2. Your trouble with bindings may be caused by a bug related to bindings detection that we patched in subsequent versions. Try upgrading to the latest versions of the constituent buildpacks and let us know if your problem persists! |
Beta Was this translation helpful? Give feedback.
-
|
How can I specify the version? |
Beta Was this translation helpful? Give feedback.
-
|
Just like this? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you could use However, the |
Beta Was this translation helpful? Give feedback.
-
|
ok, I will try tomorrow |
Beta Was this translation helpful? Give feedback.
-
|
What is the tag of the latest paketobuildpacks/builder image? I tried latest, but npm-install buildpack is not the latest version |
Beta Was this translation helpful? Give feedback.
-
|
I tried both the |
Beta Was this translation helpful? Give feedback.
-
|
Your issue is that you are setting |
Beta Was this translation helpful? Give feedback.
-
|
Oh I totally missed the |
Beta Was this translation helpful? Give feedback.
-
|
Yeah that's odd. Unfortunately, I'm not familiar enough with the concept of Some additional context: The current npm-install buildpack is v0.10.8. And the I also notice that your output contains: Do you possibly have some sort of other config - e.g a project.toml file? That might be irrelevant too, I just want to get a clear picture of what your app looks like. |
Beta Was this translation helpful? Give feedback.
-
|
The environment variable |
Beta Was this translation helpful? Give feedback.
-
|
@Sunny-001 Are you describing a new problem you're encountering re: |
Beta Was this translation helpful? Give feedback.
-
|
yes |
Beta Was this translation helpful? Give feedback.
-
|
To keep things organized, can you please file an issue on the Nodejs buildpack repository? Adding some reproduction steps and full log output on your issue will help the Nodejs maintainers resolve your issue. |
Beta Was this translation helpful? Give feedback.
-
|
18/5000 |
Beta Was this translation helpful? Give feedback.
-
I changed the nodejs download address to my private server and executed "./scripts/package.sh --version 0.5" in the build folder to generate the following file
then used the following command to build the image,but the process had an error
pack build registry.cn-hangzhou.aliyuncs.com/kpack/ruoyi-ui:2.0.0 --builder registry.cn-hangzhou.aliyuncs.com/kpack/paketo-buildpacks-builder:base -b build/buildpack.tgz --env "BP_NODE_RUN_SCRIPTS=build:prod" --env "NODE_ENV=development" --pull-policy if-not-present --path /data/build-package-sample/buildpack-test/ruoyi-ui
===> DETECTING
[detector] ERROR: No buildpack groups passed detection.
[detector] ERROR: Please check that you are running against the correct path.
[detector] ERROR: failed to detect: no buildpacks participating
ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 20
Beta Was this translation helpful? Give feedback.
All reactions