May-29th-2020, 04:21 PM
(This post was last modified: May-29th-2020, 09:03 PM by Armin@netPI.)
Hello Stephane,
the cross build "stuff" is still in there, but outsourced in a different file to be compliant with Docker Hub builds and its possibilities. (I learn every day more and more about Docker)
Now it is in the file https://github.com/HilscherAutomation/ne.../pre_build
Take this file on your AMD machine and name it e.g. pre_build.sh and call it exactly one time prior your build process. It will install a QEMU processor emulator setup in a container and sets some references. After this you can start the build process as usual and it is no longer necessary to call the "old" start and end scripts located in the previous Dockerfiles during a build process any more.
This step is a prestep that is necessary if we want to support multiarchitecture capable containers builds in future as described here https://github.com/ckulka/docker-multi-arch-example
Thx
Armin
the cross build "stuff" is still in there, but outsourced in a different file to be compliant with Docker Hub builds and its possibilities. (I learn every day more and more about Docker)
Now it is in the file https://github.com/HilscherAutomation/ne.../pre_build
Take this file on your AMD machine and name it e.g. pre_build.sh and call it exactly one time prior your build process. It will install a QEMU processor emulator setup in a container and sets some references. After this you can start the build process as usual and it is no longer necessary to call the "old" start and end scripts located in the previous Dockerfiles during a build process any more.
This step is a prestep that is necessary if we want to support multiarchitecture capable containers builds in future as described here https://github.com/ckulka/docker-multi-arch-example
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
