0

**i want to use version 11.0.19 instead of 17.0.7. So am trying the binding/Dependency Mapping to implement this **

getting beow ERROR after executing command

BellSoft Liberica JDK 11.0.19: Contributing to layer

Downloading from https://github.com/bell-sw/Liberica/releases/download/11.0.19%2B7/bellsoft-jdk11.0.19+7-linux-amd64-full.tar.gz
Verifying checksum
unable to invoke layer creator
unable to get dependency jdk
sha256 for /tmp/138f8bd3801445391ff19d683ea7f3c4662dcd0e2cd0b8ab2a5d3966b05124f8/bellsoft-jdk11.0.19+7-linux-amd64-full.tar.gz bdea11a7029e5956e9f53ce2429c185c5657c1639c1555d48306fa0b20a20b58 does not match expected 138f8bd3801445391ff19d683ea7f3c4662dcd0e2cd0b8ab2a5d3966b05124f8
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

while creating image from source code using buildpacks, by default it is using below version, when i used paketobuildpacks/builder:base as a builder.

**Bell Soft Liberica JDK 17.0.7: Contributing to layer**
    Downloading from https://github.com/bell-sw/Liberica/releases/download/17.0.7+7/bellsoft-jdk17.0.7+7-1inux-amd64.tar.gz 
Verifying checksum 
Expanding to / layers/paketo-bu ildpacks_bellsoft-liberica/jdk 
Adding 137 container CA certificates to JVM truststore 
Writing env. build/ JAVA HOME.override 
Writing env. build/ JDK HOME.override

executed below command

pack build binding_test:aug11 --path . --volume /home/ubuntu/bellsoft-jdk-config:/platform/bindings/bellsoft-jdk-config --env BP_JVM_VERSION=11.0.19 --builder paketobuildpacks/builder:base

steps followed. as mentioned in LINK

echo "https://github.com/bell-sw/Liberica/releases/download/11.0.19%2B7/bellsoft-jdk11.0.19+7-linux-amd64-full.tar.gz" >> 138f8bd3801445391ff19d683ea7f3c4662dcd0e2cd0b8ab2a5d3966b05124f8

created file type as below

echo "dependency-mapping" >> type

created folder structure like below

/bellsoft-jdk-config
├── 138f8bd3801445391ff19d683ea7f3c4662dcd0e2cd0b8ab2a5d3966b05124f8
└── type

Please help me where am doing it wrong.

deepak bolisetti
  • 1
  • 1
  • Please don't post images of text, but the text directly. – dcolazin Aug 22 '23 at 15:01
  • First thing, the easiest way to set up bindings is with binding-tool. You tell it which buildpack, and it'll download the dependencies and make the bindings for you. Then all you need to do is mount the volume, which it can even help you do also. https://github.com/dmikusa/binding-tool. Even if you don't want to use this tool, it's a good example of what you need to do for bindings to work, you could start with what it generates and modify them as well. – Daniel Mikusa Aug 23 '23 at 12:15
  • Second thing, if you want to troubleshoot your set up you need to post more info. Need to know what you're putting into the binding files, i.e `type` and `138f...`. Then we need to see the output of running the build with the dep mapping binding present. Lastly, I would suggest running the build a second time with these additional arguments `pack build -v -e BP_DEBUG=true ...` because it'll give some more helpful debug information. – Daniel Mikusa Aug 23 '23 at 12:18
  • added binding files content in the question and have also ran the build now adding DEBUG variable. No helpful info in the debug logs. – deepak bolisetti Aug 30 '23 at 16:41

0 Answers0