-
Notifications
You must be signed in to change notification settings - Fork 904
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
CacheLocation parameter not respected during downloading packages #1591
Comments
Check the CacheLocation for downloaded installers. They're probably there. REF: info at #1592 |
p.s. You really should consider using my choco-cleaner: You really should try setting cacheLocation to a shared drive for your setup. If you're not running a licensed version of Chocolatey with internalized packages take a look at this: |
Can't use your choco-cleaner because the profile size of 1 GB is too small for packages with e.g. 4 GB. We need a way to define the download location (or download location should be cacheLocation). |
I'm not following you. The choco-cleaner package is 16 KB. |
...and I think you're bumping up against a NuGet problem, not a Chocolatey problem; i.e. Chocolatey is built on top of NuGet. So NuGet puts the packges in a particular place and Chocolatey extracts them in another. choco-cleaner cleans up both locations. |
Let me try again: Didn't know that it's caused by NuGet, so thanks for the info. |
OK. I missed it was the problem of a SINGLE package size being to big. Gotcha now. Just found this, I have not tried it. Maybe you can experiment and report back: https://stackoverflow.com/questions/47860222/change-nuget-package-location-folder
|
@buenyamin, any luck? |
Couldn't try it yet, will do and post results here. |
@buenyamin I don't see a repo from the logs, just that Chocolatey thought to go look in |
I am basing this on inspecting the logs you put here - |
I'm also going to note this is output from the command line - I'm looking for the log file where more information tends to end up that is only logged there. |
I believe I am encountering the same bug. I'm trying to set a cache location for a single package, but while the In this case, the package is being installed by SYSTEM, so the profile location is not a normal user. Nevertheless, while the |
It looks like this issue was resolved with the uplift in Chocolatey 2.0.0 (or possibly a subsequent release). I can confirm that I see this behaviour in 1.4.0, but not in 2.3.0. Based on that, I will close this issue. If it's still an issue that can be reproduced on the latest Chocolatey CLI (2.3.0 as of today), then we can reopen it and update the reproduction steps. |
We have a terminal server environment where we configured UserProfileDisks with a limit of 1 GB.
Every user (also the administrative accounts) are affected by this policy. If we are trying to install a package above the profile size choco doesn't do anything or crashes (not sure).
While digging into it we saw the following behaviour.
What You Are Seeing?
choco is not using CacheLocation for downloaded packages instead it uses $env:USERPROFILE\AppData\Local\NuGet\Cache (for example C:\Users\Administrator\AppData\Local\NuGet\Cache)
What is Expected?
choco should use the defined CacheLocation
How Did You Get This To Happen? (Steps to Reproduce)
choco install packagename
Output Log
Full Log Output
The text was updated successfully, but these errors were encountered: