search

PacktPublishing / Building-Big-Data-Pipelines-with-Apache-Beam

Building Big Data Pipelines with Apache Beam, published by Packt
Apache License 2.0
83 stars 62 forks source link

Chapter 2: Step : Making our code accessible from minikube #37

Open apatre opened 1 year ago

apatre commented 1 year ago

Hi I am trying to follow the Step: Making our code accessible from Minikube. I ran the following command: ./env/install-packt-beam.sh

It is currently failing with the below error:

=> [py 6/9] RUN ln -s /usr/local/openjdk-11/bin/java /usr/bin/java                                                                                                                    0.8s 
 => [py 7/9] RUN ls /usr/src/beam-packt/                                                                                                                                               0.6s 
 => ERROR [py 8/9] RUN cd /usr/src/beam-packt/   && ./mvnw clean package -Pdocker                                                                                                      1.4s 
------
 > [py 8/9] RUN cd /usr/src/beam-packt/   && ./mvnw clean package -Pdocker:
0.625 --2023-09-09 16:33:18--  https://repo.maven.apache.org/maven2/io/takari/maven-wrapper/0.5.6/maven-wrapper-0.5.6.jar%0D
0.636 Resolving repo.maven.apache.org (repo.maven.apache.org)... 151.101.152.215, 2a04:4e42:24::215
0.729 Connecting to repo.maven.apache.org (repo.maven.apache.org)|151.101.152.215|:443... connected.
0.884 HTTP request sent, awaiting response... 404 Not Found
1.208 2023-09-09 16:33:19 ERROR 404: Not Found.
1.208
1.398 Error: Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain
1.398 Caused by: java.lang.ClassNotFoundException: org.apache.maven.wrapper.MavenWrapperMain
------
ERROR: failed to solve: executor failed running [/bin/sh -c cd /usr/src/beam-packt/   && ./mvnw clean package -Pdocker]: exit code: 1

Minikube Setup 

 minikube v1.30.1 on Microsoft Windows 11 Home Single Language 10.0.22621.2215 Build 22621.2215
❗  Kubernetes 1.25.0 has a known issue with resolv.conf. minikube is using a workaround that should work for most use cases.
❗  For more information, see: https://github.com/kubernetes/kubernetes/issues/112135
🆕  Kubernetes 1.26.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.26.3
✨  Using the docker driver based on existing profile

Could someone please help me out resolving it?