The TensorFlow OSS DevInfra Team and TF SIG Build are developing new Dockerfiles in the SIG Build GitHub repo that we want to be used for all of TensorFlow’s official build and test environments. They are published to SIG Build on DockerHub. Our first milestone is to use the Dockerfiles to build the TF Nightly packages with the following goals:
- Container-built packages are functionally identical to the current package
- Developers (you!) can build the same packages that we do with minimal effort
That milestone is ready for verification. I’ve set up internal CI jobs that use the containers to build tf-nightly packages that are very similar to the current ones, and I’d like your help to evaluate them for functional differences. Starting on Monday the 30th, we’ve been using the containers to build our official tf-nightly packages.
Here is a set of packages we built at the same commits for advance comparison. There are minor cosmetic differences but we’d like your help to find out if there are any functional differences between packages on the same row of the table below.
|Short Git Hash||Old Non-Docker Builds||New Docker Builds|
|5af3afc559||GPU Python 3.9||GPU Python 3.9|
|5af3afc559||GPU Python 3.8||GPU Python 3.8|
|5af3afc559||GPU Python 3.7||GPU Python 3.7|
|1d51452b18||CPU Python 3.9||CPU Python 3.9|
|1d51452b18||CPU Python 3.8||CPU Python 3.8|
|1d51452b18||CPU Python 3.7||CPU Python 3.7|
- Install and compare the sample packages above. If you compare the two wheels for any of the rows, do they have any differences that would affect your workflow?
- Check out the containers on DockerHub and the tf-nightly build instructions at the SIG Build repository. Are you able to build TensorFlow with them? If you use the same git hashes as above, how is your package different?
- With the new packages that came out starting on Nov. 30, is anything different about them in a way that affects your workflow?
Please give all feedback in this thread. Thank you for your help!