Had the same error and this helped me, thanks.

For completeness, I got things to work by modifying the 'bin\docker_run.cmd' script as follows:I removed these lines: for /F "tokens=* USEBACKQ" %%f in (`docker images -q %imageurl%`) do ( set location=%%f ) This results in suboptimal performance on startup, as the image get's re-loaded into doc...

No, unfortunately none of the suggestions fixed my problems. I found a workaround by modifying the "docker_run.cmd" temporarily, but I wouldn't call this a proper fix.

I'm afraid all your suggestions mean you might have missed some of my updates.Everything works if I comment out the "for loop" checking the docker image existence inside the docker_run.cmd .

Ok, I know even more now. That image isn't supposed to exist on docker hub. The script is meant to ignore the blank result and load the image from a 'lib' subdirectory. Unfortunately the 'for' command I quoted previously behaves not as expected. I see this in the batch script output: C:\Users\wojtek...

Thanks for all your suggestions so far. I pretty much followed them exactly always getting the same error result every time.But now I've managed to narrow it down a little, by logging the 'docker_run,cmd' execution. It fails on the following line:for /F "tokens=* USEBACKQ" %f in (`docker images -q a...

Thank you for response. I tried the few things you suggested, but it seems the problem might be something different. Here is the output of the commands:C:\Users\wojtek\aem-sdk\dispatcher>bin\docker_run src host.docker.internal:4503 8080 to was unexpected at this time. C:\Users\wojtek\aem-sdk\dispat...

Hello, I'm starting my journey, so I don't know much about AEM. I'm trying to setup the local environment to run some tutorials on Windows 11. Following the installation guide at https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/dispa...