Closed Doooooo0o closed 2 years ago
Using the README.md instructions to build the docker
$ docker build . -t tlsscanner STEP 1: FROM maven:3.6.1-jdk-8 AS build-image STEP 2: WORKDIR /build --> Using cache 16a985e05e4adbfae9ae1c414a41bd606896da2792ef47c448a2c154f3465e79 --> 16a985e05e4 STEP 3: RUN git clone https://github.com/RUB-NDS/TLS-Scanner.git --recurse-submodules --> Using cache 72a9309a7c4e9c458c0747077a1cac4b192d31c1808ec94f65c441208251e423 --> 72a9309a7c4 STEP 4: WORKDIR /build/TLS-Scanner --> Using cache 657586fc119af18078efcdbdfd5020bf8df45c67933b009340a0bb2f8469100a --> 657586fc119 STEP 5: RUN mvn clean install -DskipTests=true --> Using cache 15f5140a03e7879c738c570dca42d7f7c23304c4c9ccf0454f404bec716e98b4 --> 15f5140a03e STEP 6: FROM openjdk:8-alpine STEP 7: COPY --from=build-image /build/TLS-Scanner/apps /apps --> Using cache abffe5c0c40ab0021976a32a236b3d8b6ed9b784d13148fb8ea1ed5a174cb89c --> abffe5c0c40 STEP 8: WORKDIR /apps --> Using cache 6f87a199faaa4e4190d9a1e2b1c351d1a42fd22d9273058e8286d48a28c3f1cd --> 6f87a199faa STEP 9: ENTRYPOINT ["java", "-jar", "TLS-Scanner.jar"] --> Using cache 3168de0fc6be91fb344bcaeb1b5d01a6fbe3537a8e6101e11067bba1ba77a7f9 STEP 10: COMMIT tlsscanner --> 3168de0fc6b 3168de0fc6be91fb344bcaeb1b5d01a6fbe3537a8e6101e11067bba1ba77a7f9
$ docker run -t tlsscanner Error: Unable to access jarfile TLS-Scanner.jar
My guess is that the jar is not build with this name:
/apps # find . ./TLS-Server-Scanner.jar ./TLS-Client-Scanner.jar ./lib ./lib/jcommander-1.78.jar ./lib/istack-commons-runtime-3.0.11.jar ./lib/opentest4j-1.2.0.jar ./lib/guava-29.0-jre.jar ./lib/X509Attacker-1.1.0.jar ./lib/Utils-3.6.0.jar ./lib/log4j-api-2.13.3.jar ./lib/junit-platform-engine-1.5.2.jar ./lib/javassist-3.26.0-GA.jar ./lib/junit-platform-commons-1.5.2.jar ./lib/jaxb-runtime-2.3.3.jar ./lib/siv-mode-1.4.0.jar ./lib/jackson-dataformat-yaml-2.10.0.jar ./lib/jaxb-api-2.3.1.jar ./lib/txw2-2.3.3.jar ./lib/bcprov-jdk15on-1.64.jar ./lib/javax.activation-api-1.2.0.jar ./lib/jakarta.xml.bind-api-2.3.3.jar ./lib/snakeyaml-1.24.jar ./lib/junit-jupiter-engine-5.5.2.jar ./lib/json-simple-1.1.1.jar ./lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar ./lib/Attacks-3.6.0.jar ./lib/junit-jupiter-api-5.5.2.jar ./lib/slf4j-api-1.7.30.jar ./lib/failureaccess-1.0.1.jar ./lib/slf4j-log4j12-1.7.30.jar ./lib/reflections-0.9.12.jar ./lib/ModifiableVariable-3.0.0.jar ./lib/apiguardian-api-1.1.0.jar ./lib/dnsjava-2.1.9.jar ./lib/log4j-core-2.13.3.jar ./lib/joda-time-2.10.5.jar ./lib/jsr305-3.0.2.jar ./lib/jackson-databind-2.10.0.jar ./lib/checker-qual-2.11.1.jar ./lib/jackson-core-2.10.0.jar ./lib/commons-lang3-3.11.jar ./lib/Asn1Tool-1.2.0.jar ./lib/commons-math3-3.6.1.jar ./lib/log4j-1.2.17.jar ./lib/Transport-3.6.0.jar ./lib/TLS-Server-Scanner-4.0.0.jar ./lib/TLS-Scanner-Core-4.0.0.jar ./lib/bcpkix-jdk15on-1.60.jar ./lib/TLS-Core-3.6.0.jar ./lib/jackson-annotations-2.10.0.jar ./lib/error_prone_annotations-2.3.4.jar ./lib/j2objc-annotations-1.3.jar ./lib/jakarta.activation-api-1.2.2.jar
Oh you are right. I forgot to adjust it. The correct name is ./TLS-Server-Scanner.jar
Should be fixed in current master
Context
Using the README.md instructions to build the docker
Log
My guess is that the jar is not build with this name: