When I attempt to create the project a failure occurs while opening up inside the container.
[internal] load metadata for Docker Hub
503b24ecfc1e897a40a56c62c9f077c2a08d2eb8a:failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
To anyone curious, I can get past it by replacing ‘sha256:4d7409b2e3e6360bc9b5d00503b24ecfc1e897a40a56c62c9f077c2a08d2eb8a’ with ‘torizon/debian-cross-toolchain-arm64:2-bullseye’ in the Dockerfile, however, when the container does finally load, Torizon Backend refuses to load.
Some clarifying questions. Are you using the stable or early access version of the extension? Finally could you provide the contents of your project’s config_app* folder. I’m curious why the extension generated a Dockerfile with that hash as the base image.
Finally could you elaborate on refuses to load? Like does the extension hang somewhere in particular or does it just not start anymore? Is there any logs you might be able to provide about this?
@jeremias.tx I’m using the early access version. I get the same SHA error regardless of extension version. I’ve attached everything below that gets generated when choosing ‘Torizon/C-C++: Create C/C++ application’.
If I modify the Dockerfile as states above, then the app will continue to open in the container but I will get the notification that the Torizon extension isn’t loading. The extension gives the notification in the bottom right hand corner and sits and spins at ‘Initializing Torizon Extension: is Torizon Backend running?’. If I try and run the application (hitting F5) I get an error that reads ‘launch: property ‘program’ is missing or empty’.
Again, I’m trying to follow the tutorial here to attempt to launch and run a C++ application container on my Verdin dev board.
Ok I believe I found the issue. It seems the latest version of Docker Desktop turns on something by default that breaks compatibility with our extension here.
Go to the settings window of docker desktop and to the docker engine tab. You’ll see there’s a json file you can edit there. You need to edit it to look like this:
Basically just remove the “buildkit” and “features” node from the json file. These are the offending features that break compatibility with our extension. Once you’ve changed this file apply and reload the Docker Desktop. Try running the sample again it should build the dev container now.