Import containers from registries
You can bring your existing linux containers from Docker Hub,
Red Hat Quay.io, Azure, Google container registries.
To reuse containers without fetching them everytime or associate the same container across multiple projects,
a private registry is also provided for your DevCloud account.
Import from external registry
Enter the required details for importing from a
public
container registry.- Container Url:Repository URL with a tag, e.g. for docker hubdocker.io/user/repo:tag
- Add this to internal registry:To reimport the container quickly in another project.
- Container Name:Unique identifier to recognize across other Container Playground views.
To import from a
private
registry, ensure Private
is checked and enter the additional details.- Registry Server URL:e.g. for docker hub private repositoryhttps://docker.io
- Username:username used to log in to your registry
- Password:your private registry password
- The Url for AWS will be in the form of<aws_account_id>.dkr.ecr.<region>.amazonaws.com/<container_name>:<tag>and<container_name>.azurecr.iofor Azure.
- To import from AWS ECR private registry, first make sure your IAM user is assigned AmazonEC2ContainerRegistryReadOnly and above policy. Retrieve theAccess Key ID,Secret Access Keyand use the aws configure command using the aws cli to login locally. Finally, retrieve theAWS ECR tokenusing the commandaws ecr get-login-password –region <region>which must be entered in thepasswordfield.
- To import from Azure ACR private registry, setup and retrieve theusernameandpasswordfromSettings>Access Keysfrom the Azure portal.
Import from internal registry
Use this option to select a container previously imported with the
Add this to internal registry
option.
Check all the containers from list of containers you would like to associate with this project.
Click
import
on the bottom right to view the list of containers associated with the current
project. You can also continue importing additional containers with +Add new Containers
option.See Configure imported containers and Select hardware and launch containers to launch.
Try out the above flow with an example container from a respository:
- Project Name:onnxep-project
- (Import From External Registry) Container Url:default-route-openshift-image-registry.apps.cfa.devcloud.intel.com/devcloud-ri/onnxep:latest
- Container Name:onnxep-container
Before launching, Configure imported containers to view the input image and classification result of the
OpenVINO™ Execution Provider for ONNX Runtime container in your filesystem.
- Mount Point:/home/openvino
- Results Path:/home/onnxruntimedev