Not able to run local dispatcher on Windows 10 Pro | Community
Skip to main content
New Participant
June 30, 2021
Solved

Not able to run local dispatcher on Windows 10 Pro

  • June 30, 2021
  • 2 replies
  • 2410 views

Hi Guys,

 

Getting error "Required image not found, trying to load from archive...  unsupported os linux" when tried setting up Dispatcher locally. I have made sure Docker is up and running but still the error. 

 

I am following below doc from Adobe and using AEM as cloud service

 

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/dispatcher-tools.html

 

 

Appreciate help and Thanks in advance, below are is what i see when commands ran on cmd windows 10 pro

 

C:\aem-instances\dispatcher>bin\validator full -d out src
Cloud manager validator 2.0.32
2021/06/30 14:57:17 No issues found
2021/06/30 14:57:17 Dump folder already exists and non-empty: out

C:\aem-instances\dispatcher>bin\docker_run out host.docker.internal:4503 8080
values.csv found in deployment folder: C:\aem-instances\dispatcher\out - using files listed there
Required image not found, trying to load from archive...
unsupported os linux

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by BimmiSo

Hi @imalakaamir ,

Please remove hyphen from aem-instances folder and run the command again.

else Please go through the below blog

https://bimmisoi.blogspot.com/2021/05/local-dispatcher-setup-aem-as-cloud-on.html

 

Hope it helps

Thanks

 

2 replies

BimmiSoAccepted solution
Employee
June 30, 2021

Hi @imalakaamir ,

Please remove hyphen from aem-instances folder and run the command again.

else Please go through the below blog

https://bimmisoi.blogspot.com/2021/05/local-dispatcher-setup-aem-as-cloud-on.html

 

Hope it helps

Thanks

 

New Participant
July 1, 2021
Hi @bimmiso, Thanks for sharing link.
Ritesh_Mittal
New Participant
June 30, 2021

Hi @imalakaamir ,

 

Though I believe you must have noticed but in case if missed -

 

"Windows users cannot have any spaces or special characters in the path to the folder containing the Local Dispatcher Tools."

Also, try running command prompt/power shell as administrator. Try using latest/different SDK.