Kevin-Mok / kogito-images

Images for Kogito
http://kogito.kie.org
Apache License 2.0
0 stars 1 forks source link

Error running s2i command on laptop #1

Closed Kevin-Mok closed 4 years ago

Kevin-Mok commented 4 years ago

I'm having trouble running this command from this example on my work laptop:

s2i build https://github.com/kiegroup/kogito-examples.git \
    --ref master \
    --context-dir rules-quarkus-helloworld \
    quay.io/kiegroup/kogito-quarkus-ubi8-s2i:latest \
    rules-example:1.0

Despite having the same versions of s2i and Maven on both my laptop and personal PC (1.3.0 and 3.6.3), the laptop is having this error where my PC isn't:

Provided memory () limit is not valid, native build will use all available memory
---> Building application from source...
[INFO] Scanning for projects...
[INFO] Downloading from jboss-public-repository-group: https://repository.jboss.org/nexus/content/groups/public/org/kie/kogito/kogito-examples/8.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata org.kie.kogito:kogito-examples:8.0.0-SNAPSHOT/maven-metadata.xml from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org: Name or service not known
[INFO] Downloading from jboss-public-repository-group: https://repository.jboss.org/nexus/content/groups/public/org/kie/kogito/kogito-examples/8.0.0-SNAPSHOT/kogito-examples-8.0.0-SNAPSHOT.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.kie.kogito.examples:rules-quarkus-helloworld:8.0.0-SNAPSHOT: Could not transfer artifact org.kie.kogito:kogito-examples:pom:8.0.0-SNAPSHOT from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org and 'parent.relativePath' points at wrong local POM @ line 5, column 11
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.kie.kogito.examples:rules-quarkus-helloworld:8.0.0-SNAPSHOT (/tmp/src/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.kie.kogito.examples:rules-quarkus-helloworld:8.0.0-SNAPSHOT: Could not transfer artifact org.kie.kogito:kogito-examples:pom:8.0.0-SNAPSHOT from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org and 'parent.relativePath' points at wrong local POM @ line 5, column 11: Unknown host repository.jboss.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
Build failed
ERROR: An error occurred: non-zero (13) exit code from quay.io/kiegroup/kogito-quarkus-ubi8-s2i:latest

It seems that the root of the issue seems to come from these lines in particular:

[WARNING] Could not transfer metadata org.kie.kogito:kogito-examples:8.0.0-SNAPSHOT/maven-metadata.xml from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org: Name or service not known
[FATAL] Non-resolvable parent POM for org.kie.kogito.examples:rules-quarkus-helloworld:8.0.0-SNAPSHOT: Could not transfer artifact org.kie.kogito:kogito-examples:pom:8.0.0-SNAPSHOT from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org and 'parent.relativePath' points at wrong local POM @ line 5, column 11

However, this doesn't seem to make sense given that it works on my PC. When running the s2i using local files (s2i build . quay...), the same errors are produced:

Provided memory () limit is not valid, native build will use all available memory
---> Building application from source...
[INFO] Scanning for projects...
[INFO] Downloading from jboss-public-repository-group: https://repository.jboss.org/nexus/content/groups/public/org/kie/kogito/kogito-examples/0.10.0/kogito-examples-0.10.0.pom
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/kie/kogito/kogito-examples/0.10.0/kogito-examples-0.10.0.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.kie.kogito.examples:rules-quarkus-helloworld:0.10.0: Could not transfer artifact org.kie.kogito:kogito-examples:pom:0.10.0 from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org: Name or service not known and 'parent.relativePath' points at wrong local POM @ line 5, column 11
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.kie.kogito.examples:rules-quarkus-helloworld:0.10.0 (/tmp/src/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.kie.kogito.examples:rules-quarkus-helloworld:0.10.0: Could not transfer artifact org.kie.kogito:kogito-examples:pom:0.10.0 from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): repository.jboss.org: Name or service not known and 'parent.relativePath' points at wrong local POM @ line 5, column 11: Unknown host repository.jboss.org: Name or service not known -> [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
Build failed
ERROR: An error occurred: non-zero (13) exit code from quay.io/kiegroup/kogito-quarkus-ubi8-s2i:latest
Kevin-Mok commented 4 years ago

Was related to networking issues with Docker, possibly due to the way I installed Docker using this hacky method since it isn't available for Fedora 32. Fixed by installing moby-engine instead.