Greetings @BernhardG,
When the extension creates your container image it creates a local registry on the same PC you are running the extension. This is to use as an intermediary storage for your container images while you’re developing.
Now what looks like is happening here is that the extension is trying to access your container image via this identifier 10.100.19.205:5002/bgcplus-debug:arm64, but for some reason this isn’t being found. Could you try pulling this image from your local registry and confirm whether that is the case or not.
Also what version of the extension are you using and on what platform? (Linux/Windows)
Best Regards,
Jeremias