Upgrade Microsoft containers from v2.1 to v3.0 (Custom Container)

Rikesh Raj 0 Reputation points Microsoft Vendor
2024-04-08T13:38:53.45+00:00

One of our customers is assessing to upgrade their current Microsoft containers from v2.1 to v3.0, and technical team wanted to check on the below queries.

  1. Regarding the 3.0 containers (model 22-08-2023), Template container/layout start up with Using /share for shared mounts. They are expecting this container to log out Using /shared for shared mounts as they have specified in our configuration: Mounts__Shared: /shared and Mounts__Output: /logs. After doing a Docker inspect on the provided container version the above environment variables should be correct. They have checked the v2.1 containers and it correctly log out Using /shared for shared mounts.

Can you comment on above.

Using API key for authentication.

  1. They would like to understand exactly what is stored in the persistent volumes. After specifying the above configuration /shared is empty. They are expecting it to contain similar metadata as with 2.1 container.

 

  1. When they restart for example the template container, it seems the model needs to be retrained, so some metadata is not persistent. Is it anyway related to point 1?
Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
393 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
643 questions
Azure AI Document Intelligence
Azure AI Document Intelligence
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
1,388 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anveshreddy Nimmala 2,465 Reputation points Microsoft Vendor
    2024-04-15T02:46:37.2033333+00:00

    Hello Rikesh Raj,

    Welcome to microsoft Q&A, Thankyou for posting your Query here.

    Ensure that Mounts__Shared is indeed set to /shared.

    Use the docker inspect command to review the environment variables and mount points in the container configuration to confirm they match as expected.

    Look for Mounts__Shared and Mounts__Output in the environment variables section.

    check the "Mounts" section to see if /shared and /logs are correctly mounted.

    use a simple script to echo these values. 

    echo "Shared Mount: $Mounts__Shared"
echo "Output Mount: $Mounts__Output"

    Make sure that the Mounts__Shared points to a Docker volume that is intended for persistence.

    Hope this helps you.

    0 comments