Maximo

 View Only

  • 1.  Unable to mirror MAS8 images using MAS CLI

    Posted Tue January 02, 2024 03:26 PM
    I'm trying to mirror the MAS8 images to Azure Container Registry (ACR) using MAS CLI.I am following two-Phase Image Mirroring. i.e First mirror to local file system and then mirror the images from file system to registry.
     
    I am receiving below error when I mirror images from filesystem to registry. Please let me know if there any inputs on this error.
     
    Error message:
     
    - 'info: Planning completed in 30.01s'
        - 'error: unable to push file://cpopen/ibm-maximo-operator-catalog: failed to upload blob sha256:46ba3f23f1d3fb1440deeb279716e4377e79e61736ec2227270349b9618a0fdd: Get "http://acrsamplereg******.azurecr.io:5000/v2/": dial tcp IP Address:5000: i/o timeout (Client.Timeout exceeded while awaiting headers)'
     
     


    ------------------------------
    Sunil Kumar Vemuri
    Maximo Architect
    TCS
    KY
    8596284552
    ------------------------------


  • 2.  RE: Unable to mirror MAS8 images using MAS CLI

    Posted Wed January 03, 2024 03:00 AM

    Hi Sunil,

    are You using interactive or direct mode ? 

    Are You sure that Your instance of Azure Container Registry is using port 5000 ? by default ACR is using port 443. You can try logging into this registry with Docker or Podman to verify that it is reachable.



    ------------------------------
    Witold Wierzchowski
    ------------------------------

    Original Message


  • 3.  RE: Unable to mirror MAS8 images using MAS CLI

    Posted Thu January 18, 2024 03:49 PM

    Hi Witold,

    Problem has been resolved after using port 443 and service principal to authenticate the ACR. Thanks for your inputs on this.

    Regards,

    Sunil



    ------------------------------
    Sunil Kumar Vemuri
    Maximo Architect
    TCS
    KY
    8596284552
    ------------------------------

    Original Message


  • 4.  RE: Unable to mirror MAS8 images using MAS CLI

    Posted Wed December 11, 2024 02:15 PM

    Hi,

    I am also having a problem with this. My error looks almost identical to the above one, except that it is listing the GET from localhost:5000 despite acknowledging my registry details in the confirm screen.

    Do you have any idea why it would do this?

    I have confirmed that my CLI container can reach and login to the registry which is not in localhost so I don't know why it is referencing it.

    Regards

    David S



    ------------------------------
    David Shaw
    Consultant
    SRO Solutions
    ------------------------------

    Original Message


  • 5.  RE: Unable to mirror MAS8 images using MAS CLI

    Posted Thu December 12, 2024 09:22 AM

    Hi Witold,

    I'm attempting to do the same thing and having a similar error.  I have had to use the suffix parameter as the repo I need to use is formatted registry.cloud.xxx:443/org/repo.  Once I found the suffix parameter it seems to almost work but then it stops with the exact message above except for the target repo address. Where the above message lists the azure url, mine lists localhot:5000. My system there is airgapped so I can't copy the exact message.

    Do you have any idea why it might do that?

    Regards

    Dave



    ------------------------------
    David Shaw
    Consultant
    SRO Solutions
    ------------------------------

    Original Message