You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@plc4x.apache.org by "Brian Burns (Jira)" <ji...@apache.org> on 2021/02/21 13:30:00 UTC

[jira] [Created] (PLC4X-284) Docker build not working - mvnw permission denied etc

Brian Burns created PLC4X-284:
---------------------------------

             Summary: Docker build not working - mvnw permission denied etc
                 Key: PLC4X-284
                 URL: https://issues.apache.org/jira/browse/PLC4X-284
             Project: Apache PLC4X
          Issue Type: Bug
    Affects Versions: 0.8.0
            Reporter: Brian Burns


Hello, I'm trying to install PLC4X with Docker and get a couple of errors - 

$ docker build -t plc4x .
...
Step 21/39 : COPY . /ws/
 ---> e86e4d250f0c
Step 22/39 : WORKDIR /ws
 ---> Running in b2d9525763e0
Removing intermediate container b2d9525763e0
 ---> 2d714dffc27b
Step 23/39 : RUN ./mvnw -P with-boost,with-c,with-cpp,with-dotnet,with-go,with-logstash,with-opcua-werver,with-proxies,with-python,with-logstash,with-sandbox com.offbytwo.maven.plugins:maven-dependency-plugin:3.1.1.MDEP568:go-offline -DexcludeGroupIds=org.apache.plc4x,org.apache.plc4x.examples,org.apache.plc4x.sandbox
 ---> Running in 97e09acbcdfd
/bin/sh: 1: ./mvnw: Permission denied
The command '/bin/sh -c ./mvnw -P with-boost,with-c,with-cpp,with-dotnet,with-go,with-logstash,with-opcua-werver,with-proxies,with-python,with-logstash,with-sandbox com.offbytwo.maven.plugins:maven-dependency-plugin:3.1.1.MDEP568:go-offline -DexcludeGroupIds=org.apache.plc4x,org.apache.plc4x.examples,org.apache.plc4x.sandbox' returned a non-zero code: 126

So I added a step to the Dockerfile line 72
 
RUN chmod +x ./mvnw
That got it past that error, then got another one -

Non-resolvable parent POM for org.apache.plc4x.sandbox:plc4cpp:[unknown-version]: Could not find artifact org.apache.plc4x.sandbox:plc4x-sandbox:pom:0.8.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 24, column 11

I'm not familiar with maven so am not sure how to get past it...

Thank you for any help - 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)