Stop using tensorflow-testing docker images and start using hub.docker.com/tensorflow images
See original GitHub issueThe master branch is broken because the docker image used to test on gpus is the one used to test the tensorflow source code itself. This can be considered private API.
Instead, to build our manylinux2010 wheels and test our code, we should use the official way recommended by tensorflow (the same way external users do it).
Here is the official guide: https://github.com/tensorflow/custom-op The docker images we should use are from the official dockerhub repo:
tensorflow/tensorflow:2.1.0-custom-op-gpu-ubuntu16 # gpu
tensorflow/tensorflow:2.1.0-custom-op-ubuntu16 # cpu
Those images are “manylinux2010 compatible” sort of, since it’s ubuntu.
By doing that, our testing environment will become stable again, and we shouldn’t suffer sudden build breaks.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
TensorFlow Docker Images
Official Docker images for the machine learning framework TensorFlow (http://www.tensorflow.org)
Read more >Docker - TensorFlow
The TensorFlow Docker images are tested for each release. ... To start a TensorFlow-configured container, use the following command form:.
Read more >Build your own Docker image - Valohai Help
We're using tensorflow/tensorflow here but you can use any other image as a base image. Start by finding the right base image from...
Read more >Serving ML Quickly with TensorFlow Serving and Docker
We now provide Docker images for serving and development for both CPU and GPU models. To get a sense of how easy it...
Read more >Appendix — Singularity container 2.6 documentation
For example, you might use Docker's Ubuntu image layers to create an ... You can use an existing container on Singularity Hub as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like it’s because python3.8 was added to the container.
Nice find @seanmorgan! I still think we should switch images before they do more drastic changes, if they change the cuda version, the build will break again.