docker_test_ml: remove tf1.15 for JP5.1 #228
Conversation
Add a comment on the line for l4t-tensorflow tf1.15-py3 since this tag does not exist (see [1]) for latest r35.2.1 L4T release [1]: https://catalog.ngc.nvidia.com/orgs/nvidia/containers/l4t-tensorflow/tags
|
Actually I see that it's built at e8a0401#diff-1387bd5fcae9f168e3852e4ad78f22a58661d594871f81bef70619f5ee673d42R266 just not pushed to https://catalog.ngc.nvidia.com/orgs/nvidia/containers/l4t-tensorflow/tags for some reason. We use this script to test OE4T implementation with upstream containers, see #189 - if there was a way we could share logic about which containers ultimately go to ngc and which only support build from dockerfiles this would be ideal. Let us know if we can help with this. |
|
Hi @dwalkes, we've held off on publishing the TF 1.15 container image for r35.2.1 due to security vulnerabilities in TF 1.x that are only resolved in TF 2.x. Pull statistics show the majority of users have migrated to the TF 2 version of the container, but those that still need the TF 1.15 container can build it from the dockerfile. Thanks for the PR! |
Add a comment on the line for l4t-tensorflow tf1.15-py3 since this tag does not exist (see https://catalog.ngc.nvidia.com/orgs/nvidia/containers/l4t-tensorflow/tags) for latest r35.2.1 L4T release