docker-client does not work on ARM (e.g. Raspberry Pi) #477
Comments
Workaround : Rebuild JFFI for ARM Linux from source :
and
|
This seems like an issue with jnr/jffi and not docker-client, since the logic for locating libjffi.so is located within the java code of that package. The lookup order seems to be :
From the stacktrace, it seems like the library has been located in the native jar, because getStubLibraryStream -> getResourceAsStream (in loadFromJar) has some checks to ensure the returned stream is not null, and they pass. The issue seems to be with copying the located library stream into the temporary file created on /tmp. Can you examine '/tmp/jffi8109566181291199608.so', or whichever file is mentioned during a particular run and see if it look like a proper .so file ? Would the process have read, and execute permissions on it ? It might even be worth comparing the copied .so file (for arm) to the original one in the native jar. |
yes I did that, the SO file is not arm v7, it's another architecture that Cheers, Brice On Mon, Jul 25, 2016 at 4:50 PM, Roland Grunberg notifications@github.com
|
From the stacktrace, it seems to be able to figure out that the cpu is arm, and assuming System.getProperty("os.name") resolves to 'Linux', it should be loading the correct .so. Perhaps what is being shipped in maven-central in jffi-native is simply not what your arm v7 processor supports. A 'file' call on the arm .so gives : file jni/arm-Linux/libjffi-1.2.so |
+1 |
Closing as people have said it's an issue with jffi. |
Hi -- I know this is already a closed thread, but I wanted to check with you folks here to see if you have ran into the same issue I have in #743 ? I can't get the container stats without getting an exception. |
Description
While using docker-client through the docker-maven-plugin on a Raspberry Pi (debian jessie), the wrong JFFI shared library is being used (it should refer to the ARM library build).
How to reproduce
invoke :
mvn docker:build
What do you expect
The build should complete and the docker image be made available.
What happened instead
Software:
Full backtrace
The text was updated successfully, but these errors were encountered: