Error in Dispatcher Setup on Local using dispatcher-sdk-2.0.91 | Community
Skip to main content
N
nitinp46101556
May 14, 2022

Error in Dispatcher Setup on Local using dispatcher-sdk-2.0.91

  • May 14, 2022
  • 3 replies
  • 2065 views

Hello 

 

Trying to do dispatcher(dispatcher-sdk-2.0.91) set up on Mac following https://github.com/adobe/aem-enablement/tree/master/AEMAsACloudService/08_Dispatcher_SDK_Validator documentation .

 

Able to execute till Step 3 but while executing Step 4 i.e. Running "./bin/docker_run.sh ./out docker.for.mac.localhost:4503 8080" command getting  

"docker: invalid reference format: repository name must be lowercase."  error 

 

Can anyone help me identify the root cause of the issue .

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

3 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
May 14, 2022

Dear @nitinp46101556 

 

Presumably your docker is up and running on specific port (eg. 8081), Can you try this below command once?

./bin/docker_run.sh ./src host.docker.internal:4503 8081


Let me know if still any concern.

 

Regards,

Santosh

 

Santosh Sai
    N
    nitinp46101556Author
    May 16, 2022

    No above solution didn't work 

      SantoshSai
      Community Advisor
      SantoshSaiCommunity Advisor
      Community Advisor
      May 16, 2022

      @nitinp46101556 

      Could you please give us log details here?

       

      Thanks!

      Santosh Sai
        Vijayalakshmi_S
        Vijayalakshmi_S
        Level 10
        May 17, 2022

        @nitinp46101556 

        Can you confirm the folder name (where out is located) is without spaces. Ignore, if it is. 

          F
          feolinaresm
          September 20, 2023

          I'm having the same issue and checked that the folder where out is located has no unwanted stuff, but this continues with the same issue, any thoughts?

          F
          feolinaresm
          September 20, 2023

          I ran into the same issue just a couple of hours ago and hope this helps you out of this situation:

          - By now you should already have your dispatcher image available on your docker dashboard, right?

          - As a workaround to this situation you can just run it directly from there, adding some environment variables on the "optional settings" panel to it:

          those are the AEM_PORT and the AEM_HOST which are the ones related to your publish instance, in my case "docker.for.mac.localhost" and "4503" respectively.

           

          I'm still trying to find the origin of this situation, but for now, this workaround can help us to continue without any blockers.

           

          Terms & ConditionsAccessibility statement

          Loading footer...