saymrwulf/onnxruntime
1
0
Fork 0
mirror of https://github.com/saymrwulf/onnxruntime.git synced 2026-07-28 20:11:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add usage details of unified MCR container image (#6182)

Browse source 
Going forward, a single unifed docker image will be published in
MCR. The hardware accelerator target choice will have to be made
in the application using OpenVINO EP's runtime config options.
This commit is contained in:
S. Manohar Karlapalem 2020-12-21 11:48:54 -08:00 committed by GitHub
parent 201d0dbb1a
commit ea9cfa554a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
dockerfiles/README.md
View file

@ -86,6 +86,12 @@ Use `docker pull` with any of the images and tags below to pull an image and try
**Ubuntu 18.04, Python & C# Bindings**
### **1. Using MCR container images**
The unified MCR container image can be used to run an application on any of the target accelerators. In order to select the target accelerator, the application should explicitly specifiy the choice using the *device_type* configuration option for OpenVINO Execution provider. Refer to [OpenVINO EP runtime configuration documentation](https://github.com/microsoft/onnxruntime/blob/master/docs/execution_providers/OpenVINO-ExecutionProvider.md#runtime-configuration-options) for details on specifying this option in the application code.
If the *device_type* runtime config option is not explicitly specified, CPU will be chosen as the hardware target execution.
### **2. Building from Dockerfile**
1. Build the onnxruntime image for one of the accelerators supported below.
Retrieve your docker image in one of the following ways.