build image un-idempotency about java

[TianMing2018]

It seems that the builder crushed when it try to bind volume to buildpack ,cause of there was multi-version of cached jdk and syft in the volume, here is the files list in my proxy-volume,when I remove lower(or discarded) version ,I can build image successfully everytime。I'm wondering what you will do to solve this issue ? add some description in docs guides / add validation in buildpack / or just do nothing ,please leave a comment.

#### file in proxy-volume
root@ac4d547e9e30:/# ls -al
total 439080
drwxr-xr-x 2 root root      4096 Feb 18 11:38 .
drwxrwxrwt 1 root root      4096 Feb 18 11:41 ..
-rw-r--r-- 1 root root        87 Jan 29 05:57 2ea2f787065a1ac58b528a4d7db453fa0f8e05b2192300b4ea52ecf885723137
-rw-r--r-- 1 root root        75 Feb 18 11:11 30912a77b1b4a565cf6ed936ea619aa353d8d9ddc5d216afdc242cf3b1e7a0a7
-rw-r--r-- 1 root root        76 Feb 18 11:11 71296b3d87b2837aeb7e55b2ca98dc69f92c7274ae3d968698da5887b7462ad2
-rw-r--r-- 1 root root        86 Dec 17 08:27 86df083bd817970404d56d360926d440eb895041ab8d7f580d79b34b19e621e8
-rw-r--r-- 1 root root        76 Dec 17 08:33 89860504694a05a75688991ac24281cb84cfa61d48c973ddee7559fa7fc0a60e
-rw-r--r-- 1 root root        78 Jan 29 05:57 9f76c9c93748472a9f145999d4da99c1d8cb070872bba574843c45ef1d14c27f
-rw-r--r-- 1 root root 208333155 Dec 12 16:40 bellsoft-jdk11.0.17+7-linux-amd64.tar.gz
-rw-r--r-- 1 1000 1000 208389475 Jan 16 14:10 bellsoft-jdk11.0.18+10-linux-amd64.tar.gz
-rw-r--r-- 1 root root        75 Dec 19 11:29 eca042851d6dc8c2158a923aaf0736d8b9141a10ee8b77a2a45c9528ef74799b
-rw-r--r-- 1 1000 1000     61385 Jan 10 12:06 spring-cloud-bindings-1.11.0.jar
-rw-r--r-- 1 root root  20014858 Dec 14 01:40 syft_0.62.1_linux_amd64.tar.gz
-rw-r--r-- 1 1000 1000  10878369 Jan 31 17:13 syft_0.69.1_linux_amd64.tar.gz
-rw-r--r-- 1 1000 1000    837832 Jan 31 04:51 thc-x86_64-unknown-linux-musl
-rw-r--r-- 1 1000 1000   1050824 Jan  9 04:11 thc-x86_64-unknown-linux-musl.bak
-rw-r--r-- 1 root root        19 Dec 17 08:18 type

#### file content
root@ac4d547e9e30:/# cat 2ea2f787065a1ac58b528a4d7db453fa0f8e05b2192300b4ea52ecf885723137
file:///platform/bindings/dependency-mapping/bellsoft-jdk11.0.18+10-linux-amd64.tar.gz
root@ac4d547e9e30:/# cat 30912a77b1b4a565cf6ed936ea619aa353d8d9ddc5d216afdc242cf3b1e7a0a7
file:///platform/bindings/dependency-mapping/thc-x86_64-unknown-linux-musl
root@ac4d547e9e30:/# cat 71296b3d87b2837aeb7e55b2ca98dc69f92c7274ae3d968698da5887b7462ad2
file:///platform/bindings/dependency-mapping/syft_0.69.1_linux_amd64.tar.gz
root@ac4d547e9e30:/# cat 86df083bd817970404d56d360926d440eb895041ab8d7f580d79b34b19e621e8
file:///platform/bindings/dependency-mapping/bellsoft-jdk11.0.17+7-linux-amd64.tar.gz
root@ac4d547e9e30:/# cat 89860504694a05a75688991ac24281cb84cfa61d48c973ddee7559fa7fc0a60e
file:///platform/bindings/dependency-mapping/syft_0.62.1_linux_amd64.tar.gz
root@ac4d547e9e30:/# cat 9f76c9c93748472a9f145999d4da99c1d8cb070872bba574843c45ef1d14c27f
file:///platform/bindings/dependency-mapping/spring-cloud-bindings-1.11.0.jar
root@ac4d547e9e30:/# cat eca042851d6dc8c2158a923aaf0736d8b9141a10ee8b77a2a45c9528ef74799b
file:///platform/bindings/dependency-mapping/thc-x86_64-unknown-linux-musl

#### remove outdated file
root@ac4d547e9e30:/# rm eca042851d6dc8c2158a923aaf0736d8b9141a10ee8b77a2a45c9528ef74799b
root@ac4d547e9e30:/# rm thc-x86_64-unknown-linux-musl.bak
root@ac4d547e9e30:/# rm 89860504694a05a75688991ac24281cb84cfa61d48c973ddee7559fa7fc0a60e
root@ac4d547e9e30:/# rm syft_0.62.1_linux_amd64.tar.gz
root@ac4d547e9e30:/# rm 86df083bd817970404d56d360926d440eb895041ab8d7f580d79b34b19e621e8
root@ac4d547e9e30:/# rm bellsoft-jdk11.0.17+7-linux-amd64.tar.gz

[dmikusa]

Is this still an issue? I'm not seeing a specific error here? When do you see a failure and what is the exact error message you see?

[TianMing2018]

Is this still an issue? I'm not seeing a specific error here? When do you see a failure and what is the exact error message you see?
I had describe the problem below,Shortly, when we use volume to store multi jdk and others files, the build will be messed, it's difficult to tell the problem, maybe we should quote this point in documents or modify code

[dmikusa]

Is there any way you could attach a build log or other info to show what happens? I don't think I understand what you're reporting here.

I can see you're hitting some sort of issue with mapped dependencies and in particular when there are multiple versions, but I have had this case before. I frequently use mapped dependencies and haven't encountered this issue so I don't think it's an obvious problem.

I definitely want to hear more about it and try to understand what might be happening. I just need a little more info to go on, build logs showing the errors you see (or what you don't see, depending on the problem), and more concise steps to reproduce. I looked at your linked project, but I'm not exactly sure what to do with it to reproduce the problem. If you could give me a brief set of steps to reproduce, I could try that also. Thanks

[TianMing2018]

Sorry,I didn't persist log files at that moment, and I re-run test now but can't reproduction issue, So I decide to close this issue for now.