Skip to content

Latest commit

 

History

History
77 lines (49 loc) · 4.33 KB

Docker_Images_EN.md

File metadata and controls

77 lines (49 loc) · 4.33 KB
Raw

Docker Images

(简体中文|English)

This document maintains a list of docker images provided by Paddle Serving.

Get docker image

You can get images in two ways:

  1. Pull image directly from dockerhub or registry.baidubce.com through TAG:

    docker pull registry.baidubce.com/paddlepaddle/serving:<TAG>

  2. Building image based on dockerfile

    Create a new folder and copy Dockerfile to this folder, and run the following command:

    docker build -f tools/${DOCKERFILE} -t registry.baidubce.com/paddlepaddle/serving:<images-tag> .

Image description

If you want to customize your Serving based on source code, use the version with the suffix - devel.

If you need to develop and compile based on the source code, please use the version with the suffix -devel. In the TAG column, 0.9.0 can also be replaced with the corresponding version number, such as 0.5.0/0.4.1, etc., but it should be noted that some development environments only increase with a certain version iteration, so not all environments All have the corresponding version number can be used.

Development Docker Images:

A variety of development tools are installed in the development image, which can be used to debug and compile code, and adapt to two GCC versions and multiple CUDA environments, but the image size is large.

Description OS TAG Dockerfile
CPU development Ubuntu16 0.9.0-devel Dockerfile.devel
GPU (cuda10.1-cudnn7-tensorRT6) development Ubuntu16 0.9.0-cuda10.1-cudnn7-devel Dockerfile.cuda10.1-cudnn7.devel
GPU (cuda10.2-cudnn7-tensorRT6) development Ubuntu16 0.9.0-cuda10.2-cudnn7-devel Dockerfile.cuda10.2-cudnn7.devel
GPU (cuda10.2-cudnn8-tensorRT7) development Ubuntu16 0.9.0-cuda10.2-cudnn8-devel Dockerfile.cuda10.2-cudnn8.devel
GPU (cuda11.2-cudnn8-tensorRT8) development Ubuntu16 0.9.0-cuda11.2-cudnn8-devel Dockerfile.cuda11.2-cudnn8.devel

Runtime Docker Images:

Runtime Docker Images is lighter than Develop Images, and Running Images are made up with serving whl and bin, but without develop tools like cmake because of lower image size. If you want to know about it, plese check the document Paddle Serving on Kubernetes.

Env Version Docker images tag OS Gcc Version Size
CPU 0.9.0 0.9.0-runtime Ubuntu 16 8.2.0 3.9 GB
CUDA 10.1 + cuDNN 7 0.9.0 0.9.0-cuda10.1-cudnn7-runtime Ubuntu 16 8.2.0 10 GB
CUDA 10.2 + cuDNN 7 0.9.0 0.9.0-cuda10.2-cudnn7-runtime Ubuntu 16 8.2.0 10.1 GB
CUDA 10.2 + cuDNN 8 0.9.0 0.9.0-cuda10.2-cudnn8-runtime Ubuntu 16 8.2.0 10.1
CUDA 11.2 + cuDNN 8 0.9.0 0.9.0-cuda11.2-cudnn8-runtime Ubuntu 16 8.2.0 14.2 GB

Java SDK Docker Image:

registry.baidubce.com/paddlepaddle/serving:0.9.0-cuda10.2-cudnn8-java

XPU Docker Images:

registry.baidubce.com/paddlepaddle/serving:xpu-arm # for arm xpu user
registry.baidubce.com/paddlepaddle/serving:xpu-x86 # for x86 xpu user

Requirements for running CUDA containers

Running a CUDA container requires a machine with at least one CUDA-capable GPU and a driver compatible with the CUDA toolkit version you are using.

The machine running the CUDA container only requires the NVIDIA driver, the CUDA toolkit does not have to be installed.

For the relationship between CUDA toolkit version, Driver version and GPU architecture, please refer to nvidia-docker wiki.