I’m going to need a little more information to help you.
In the appconfig_0 folder there should be a file named Dockerfile.debug. If you could open a command prompt, then cd into the appconfig_0 folder and run docker build -f Dockerfile.debug this may give us some more information about what went wrong.
I also tried to follow the getting started guide on an iMX8 module, and I get exactly the same error. I’ve attached the Dockerfile.debug generated by the iMX8 project. Is it correct, that the first line states FROM arm32v7/debian:buster-slim?
I’m also wondering if there’s some missing configuration step in the guide because the build output says 1>------ Build started: Project: TorizonApp1, Configuration: Debug_Debian_Buster_slim x64 ------ no matter if I’m building for an ARM64 (iMX8) oder ARM32 (iMX6) architecture?
The newer version of the extension which is slated for release during Q1 this year will support proper arm64 containers. However compatibility wise our arm64 modules should be able to execute arm32 binaries.
As for the main issue I can only assume that you may have inadvertently changed the project configuration such that $EXTRAPACKAGES is some non standard value that causes the docker build to break.
One thing that would help clarify this is if you could share the content of the following files: Dockerfile and config.json. These files should be found in the same folder as Dockerfile.debug.
Apologies for the issues, this case has been elevated to our development team who are working on sorting the issues out with the extension. Thank you for reporting these issues however as your feedback is important.
In truth the extension spun out of a project from our innovation team and hasn’t been iterated/tested upon as much as it should have.
At the moment I can not give a definite timeline on when the extension will be fixed. But I will update this thread when I get any more information