Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggest to the user to define a cache volume for bazel #39560

Open
bhack opened this issue May 14, 2020 · 0 comments
Open

Suggest to the user to define a cache volume for bazel #39560

bhack opened this issue May 14, 2020 · 0 comments
Assignees
Labels
stat:awaiting tensorflower Status - Awaiting response from tensorflower subtype:bazel Bazel related Build_Installation issues type:build/install Build and install issues type:feature Feature requests

Comments

@bhack
Copy link
Contributor

bhack commented May 14, 2020

Thank you for submitting a TensorFlow documentation issue. Per our GitHub
policy, we only address code/doc bugs, performance issues, feature requests, and
build/installation issues on GitHub.

The TensorFlow docs are open source! To get involved, read the documentation
contributor guide: https://www.tensorflow.org/community/contribute/docs

URL(s) with the issue:

Please provide a link to the documentation entry, for example:
https://www.tensorflow.org/install/source#docker_linux_builds

Description of issue (what needs changing):

We the current info about Docker build from source we will lost the cache when we destroy the container

Clear description

The bazel cache will be stored in /root/.cache/bazel/ that it is ephemeral and so it will lost if the container it is removed. So you are going to lost hours of builds just if you will restart the image with a new container. You need to suggest to mount an host volume for the bazel cache.

For example, why should someone use this method? How is it useful?

@ravikyram ravikyram added type:build/install Build and install issues type:docs-bug Document issues subtype:bazel Bazel related Build_Installation issues and removed type:docs-bug Document issues labels May 15, 2020
@ravikyram ravikyram assigned angerson and unassigned ravikyram May 15, 2020
@ravikyram ravikyram added the stat:awaiting tensorflower Status - Awaiting response from tensorflower label May 15, 2020
@SuryanarayanaY SuryanarayanaY added the type:feature Feature requests label Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat:awaiting tensorflower Status - Awaiting response from tensorflower subtype:bazel Bazel related Build_Installation issues type:build/install Build and install issues type:feature Feature requests
Projects
None yet
Development

No branches or pull requests

4 participants