June-28th-2018, 06:58 PM
Well Flo this is easy explained why this happens.
As described in the readme of all provided examples containers the Dockerfile is supporting cross compilation on x86 machines. Since all our example containers are based on automated Docker Hub builds on Docker Hub servers - which are all x86 machines - a trick/modification of the Dockerfile allows compilation of ARM code on x86 machines.
But now you are on an ARM processor and cross compilation is no longer needed. So comment out the two lines RUN [ "cross-build-start" ] and RUN [ "cross-build-end" ] and docker build command will work as usual.
As described in the readme of all provided examples containers the Dockerfile is supporting cross compilation on x86 machines. Since all our example containers are based on automated Docker Hub builds on Docker Hub servers - which are all x86 machines - a trick/modification of the Dockerfile allows compilation of ARM code on x86 machines.
But now you are on an ARM processor and cross compilation is no longer needed. So comment out the two lines RUN [ "cross-build-start" ] and RUN [ "cross-build-end" ] and docker build command will work as usual.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)