[CLI]: `WANDB_DIR` env. var. does not affect the location of the `artifacts/` directory
See original GitHub issueI specifically set WANDB_DIR
so that I can avoid downloading large files on expensive file storage, and instead place them onto cheaper local storage. Why then does the wandb client still download gigabytes of files into the ~/my/project/artifacts
directory? What environment variable do I set to affect where wandb stores these heavyweight files?
AFAIU I don’t see any relevant variable in the official docs.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[CLI]: `WANDB_DIR` env. var. does not affect the location of ...
You can override what directory download writes to with the root argument of that method. All artifact data is written through the cache....
Read more >Environment Variables - Documentation - Weights & Biases
When you're running a script in an automated environment, you can control wandb with environment variables set before the script runs or within...
Read more >Environment variables to configure the AWS CLI
Environment variables provide another way to specify configuration options and credentials, and can be useful for scripting or temporarily setting a named ...
Read more >Using Environment Variables | Cloud Functions Documentation
These variables are scoped to the function and are not visible to other ... runtime environment variable using the Google Cloud CLI, use...
Read more >Introduction to environment variables - CircleCI
If your secrets appear elsewhere, such as test results or artifacts, they will not be masked. Additionally, values are still accessible to users...
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 FreeTop 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
Top GitHub Comments
@samuela by default when you call .download on an artifacts it’s writes that data to the current directory. You can override what directory download writes to with the root argument of that method.
All artifact data is written through the cache. You can change the location of the cache with the WANDB_CACHE_DIR environment variable.
Hey Samuel, I believe this is a current limitation. I’ll double-check whether there is a workaround for this and let you know.