The following level headings are also tags for the docker image.
py38-cuda11.0, py38
python3-libnvinfer and uff-converter-tfpy38-cuda10.2
python3-libnvinfer and uff-converter-tfpy38-cuda10.1
python3-libnvinfer and uff-converter-tfpy38-cuda10.0, py38
python3-libnvinfer and uff-converter-tfpy36-cuda11.0
py36-cuda10.2
py36-cuda10.1
py36-cuda10.0, py36
py27-cuda10.1 (no longer updated)
py27-cuda10.0, py27 (no longer updated)
To find out the specific version number of each software in the above images, please visit here.
docker pull vistart/build_tensorflow:py38-cuda11.0
The above command will pull the image that contains Python 3.8 and CUDA 11.0.
git clone -b build_tensorflow https://github.com/vistart/Dockerfiles
cd Dockerfiles
sh build_tensorflow/py38-cuda11.0/build_tensorflow_2.sh
-rw-r--r-- 1 root root 262907737 Aug 8 03:43 tensorflow-2.4.0-cp38-cp38-linux_x86_64.whl
In addition to storing all images in Docker Hub, they are also stored in the Hong Kong node of Aliyun Container Service for alternative. If you want to use the latest image as soon as possible, but Docker Hub has not been able to synchronize for a long time, you can try to use the Hong Kong node of Aliyun Container Service.
The tag name format is:
registry.cn-hongkong.aliyuncs.com/vistart_public/build_tensorflow:<tag name>
If you want to use the latest image as soon as possible, but don't want to change it's tag name. You can pull the image stored in the Docker Hub after pulling it stored in the Hong Kong node. Because the contents of the two are exactly the same, they have been tagged after pulling the manifest of the image stored in Docker Hub without pulling any image layer.
After that, if you want to update the image, repeat the above operations.
Content type
Image
Digest
Size
8.4 GB
Last updated
about 6 years ago
docker pull vistart/build_tensorflow