Paketo Buildpacks
A way to add files in the resulting image #196
Replies: 3 comments 5 replies
-
|
Another comment: I'm trying to solve the issue with spring boot plugin by adding the source-removal build pack to the build. But I'm getting this error: Pulling buildpack image 'docker.io/paketo-buildpacks/source-removal:latest' ..................................................
I cannot pull the source-removal image from any docker registry... tryed using: docker pull /paketo-buildpacks/source-removal How to add the source-removal buildpack? I don't think adding the gradle buildpack is the correct answer because spring boot plugin is able to generate the image without using it to build the app. |
Beta Was this translation helpful? Give feedback.
-
|
Second note: adding the gradle buildpack but is not picked by the plugin command. I think it is explicity disabled by the plugin |
Beta Was this translation helpful? Give feedback.
-
|
Things are different from the command line and from Spring Boot's plugin. The Spring Boot plugin will compile your application locally and then build the image from your executable JAR. By default, When you try to tell it to retain files and you use the Spring Boot plugin, it doesn't work because those files are already gone (or at the least, in a different folder structure because they are in your JAR). What I would suggest is to put everything you require into your JAR file. This will ensure that it ends up in the resulting container image without any additional configuration. Everything in the JAR ends up in the image, regardless of how you build. If you cannot do that, then a couple of notes:
Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification. I did try to embed the agent in the jar with no sucess, that is why I need to copy it. Any thoughts on making this a core feature indepent of the build pack used, so it could work on any case, building from source or building locally then adding the files to the final image? |
Beta Was this translation helpful? Give feedback.
-
|
The documentation on site makes the impression that it works on any case, as if the builder resposibility not the builderpack. If not implemented as core, I suggest to clarify this behaviour in doc. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not totally sure what you mean by making it a core feature. With cloud-native buildpacks, there are very few core features, just what is built into pack (or Spring Boot plugin) and the buildpack lifecycle. Most functionality comes from the buildpacks, like we have implemented now. If you want to suggest a change for how the core works, you'd want to ask over on https://github.com/buildpacks/pack or the Spring Boot Github. I agree, it is a little confusing how you can build from both source or pre-compiled assets. The additional complexity makes for more flexibility though. I know Spring Boot uses pre-compiled assets for the reason you mentioned, it fits better into CI, among others. |
Beta Was this translation helpful? Give feedback.
-
|
I like the flexibility of the pre-compiled vs builder. In dockerfile we can direct alter the layers of to resulting image, and I understand why this is not the case here, but maybe a buildpack that is trigged in the final image builder and gives the possibility to add/remove using docker COPY API files can work on any case, I'm not sure if we need a core feature or just a specific lifecycle (I'm new to buildpacks). Anyway thanks for the clarification it solves the question. |
Beta Was this translation helpful? Give feedback.
-
If you're thinking that all buildpacks need to be like Paketo buildpacks, that's not the right picture. Paketo buildpacks are on the more complicated side of things. We optimize for a very wide range of use cases and it makes the buildpacks more complicated. If you've not done so, I would encourage you to try writing a buildpack. I hope that folks find it accessible. It minimally requires two shell scripts (or other executables). There's a great tutorial over here: https://buildpacks.io/docs/buildpack-author-guide/create-buildpack/ |
Beta Was this translation helpful? Give feedback.
-
I'm using spring boot plugin to build images, which in turn use some build pack. This is the list of buildpacks used:
paketo-buildpacks/ca-certificates 3.6.1
[creator] paketo-buildpacks/bellsoft-liberica 10.2.0
[creator] paketo-buildpacks/syft 1.28.0
[creator] paketo-buildpacks/executable-jar 6.6.3
[creator] paketo-buildpacks/dist-zip 5.5.2
[creator] paketo-buildpacks/spring-boot 5.23.0
[creator] paketo-buildpacks/environment-variables 4.5.1
When using the command line to build instead of the plugin it uses the following build pack:
paketo-buildpacks/ca-certificates 3.6.1
[detector] paketo-buildpacks/bellsoft-liberica 10.2.0
[detector] paketo-buildpacks/syft 1.28.0
[detector] paketo-buildpacks/gradle 7.1.0
[detector] paketo-buildpacks/executable-jar 6.6.3
[detector] paketo-buildpacks/apache-tomcat 7.13.0
[detector] paketo-buildpacks/apache-tomee 1.6.1
[detector] paketo-buildpacks/liberty 3.6.0
[detector] paketo-buildpacks/dist-zip 5.5.2
[detector] paketo-buildpacks/spring-boot 5.23.0
[detector] paketo-buildpacks/environment-variables 4.5.1
When I use the env variable BP_INCLUDE_FILES=newrelic/* as mentioned in the documentation. The file is not added using the plugin, but is added using the command line. Investigation shows that the buildpack which is participating and copying the artifacts is packeto-buildpackes/gradle
Other buildpack which claims to add files using this env variable is paketo-buildpacks/source-removal. But as a user I find this quite confusing and I spend 2 days figuring out why the file is not being added.
Should this behavior be independent of buildpacks added? I think this should be a core feature.
Beta Was this translation helpful? Give feedback.
All reactions