Ch04 Image-of-the-Day build

[sqlgeekster]

I got the following errors when I was building the Image-of-the-Day image. Running on Windows. Any ideas?

Thanks,
Jeff Jones

d:\GITRepo\diamol\ch04\exercises\image-of-the-day>docker image build -t image-of-the-day .
Sending build context to Docker daemon 23.04kB
Step 1/11 : FROM diamol/maven AS builder
---> 82e47db98ff5
Step 2/11 : WORKDIR /usr/src/iotd
---> Using cache
---> f495b0443b3c
Step 3/11 : COPY pom.xml .
---> Using cache
---> 8ae3e1a87c47
Step 4/11 : RUN mvn -B dependency:go-offline
---> Running in 416f5bffb0a7
[INFO] Scanning for projects...
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.1.3.RELEASE/spring-boot-starter-parent-2.1.3.RELEASE.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.sixeyed.diamol:iotd-service:0.1.0: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.1.3.RELEASE from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.1.3.RELEASE/spring-boot-starter-parent-2.1.3.RELEASE.pom and 'parent.relativePath' points
at wrong local POM @ line 10, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.sixeyed.diamol:iotd-service:0.1.0 (C:\usr\src\iotd\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for com.sixeyed.diamol:iotd-service:0.1.0: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.1.3.RELEASE from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.1.3.RELEASE/spring-boot-starter-parent-2.1.3.RELEASE.pom and 'parent.relativePath' points at wrong local POM @ line 10, column 13: Unknown host This is usually a temporary error during hostname
resolution and means that the local server did not receive a response from an authoritative server (repo.maven.apache.org) -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
The command 'powershell -Command $ErrorActionPreference = 'Stop'; mvn -B dependency:go-offline' returned a
non-zero code: 1

[gnarlygeek]

sqlgeekster, I have the same issue. Did you get any response from Elton or others on how to modify the xml file to the correct version(s)? I'm assuming the explicit version reference in the xml is the cause. Obviously, "spring" has moved on? :)

[sqlgeekster]

@gnarlygeek Never got a response.

[gnarlygeek]

Ok, just on a lark, I switched to my Windows PC with Ubuntu running under WSL2, and there are no issues. My Linux box is running CentOS 8. I've tried disabling the firewall process but that had no impact. It appears there is something in my CentOS 8 configuration that's preventing Maven from resolving the dependencies. If i figure it out, I'll post it here. Are you also trying to run this on a Linux system, and if so, what distribution and version?

[zhoukaidev]

Encounter the same issue on Linux.
Have you figured it out?
Thanks 😄

My Linux version is:

Linux 5.4.0-53-generic
#59~18.04.1-Ubuntu

[gnarlygeek]

Hello, no I did not resolve the issue on native Ubuntu. However, I found that it works if you are using WSL 2 with Ubuntu on Windows 10. Both of these Ubuntu instances were running the 18.04 release. This makes me suspect the issue may be a difference in Docker on Linux versus the Windows Docker Desktop. It would be interesting to know if someone has tried this on a CentOS or RHEL distribution? I have a VM with CentOS, but not enough free time to check it out for several weeks. As I recall, most of the other examples after this did work under Linux. I hope this helps? :> From: Kai Zhou <[email protected]> Sent: Wednesday, December 2, 2020 5:51 AM To: sixeyed/diamol <[email protected]> Cc: Tom Arthur <[email protected]>; Mention <[email protected]> Subject: Re: [sixeyed/diamol] Ch04 Image-of-the-Day build (#8) Encounter the same issue on Linux. Have you figured it out? Thanks 😄 My Linux version is: Linux 5.4.0-53-generic #59~18.04.1-Ubuntu — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsixeyed%2Fdiamol%2Fissues%2F8%23issuecomment-737152298&data=04%7C01%7C%7C9164fbd1516d4c9084f108d896b035cd%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637425030837370128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=unErP8UYtQOysLR56IWnYVPtzT4yYRZqW5ld1EieJkQ%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAELAR3RP4W3VSWZN35S6SCDSSYL2VANCNFSM4KR56NAQ&data=04%7C01%7C%7C9164fbd1516d4c9084f108d896b035cd%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637425030837380123%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BE3IB7E9G89STrfemAaOBqsLFU8wAFcWx%2B2i%2BHROyT8%3D&reserved=0>.

[JustJordanT]

Having the same issue on CentOS 4.18.0-193.28.1.el8_2.x86_64.

[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.sixeyed.diamol:iotd-service:0.1.0: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.1.3.RELEASE from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.1.3.RELEASE/spring-boot-starter-parent-2.1.3.RELEASE.pom and 'parent.relativePath' points at wrong local POM @ line 10, column 13
 @
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.sixeyed.diamol:iotd-service:0.1.0: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.1.3.RELEASE from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.1.3.RELEASE/spring-boot-starter-parent-2.1.3.RELEASE.pom and 'parent.relativePath' points at wrong local POM @ line 10, column 13

    at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:397)
    at org.apache.maven.graph.DefaultGraphBuilder.collectProjects (DefaultGraphBuilder.java:414)
    at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor (DefaultGraphBuilder.java:405)
    at org.apache.maven.graph.DefaultGraphBuilder.build (DefaultGraphBuilder.java:82)
    at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Thanks,

[jjlind000]

Hi guys
This can happen perhaps for a number of reasons but one of those reasons is being on a VPN. If you are on one, disconnect and try again. It worked for me.