Closed sykesbPragmatics closed 3 weeks ago
NuGet calls standard APIs in .NET to read and write files. I'm going to close this for now since its not really NuGet specific other than this one folder happens to be NuGet's global packages cache and it cannot write to it.
I'm not sure who would be the right person to ask about this, it seems like an easy task to solve by just granting write permissions. But this set up sounds a little more complicated than normal. I hope you get this figured out.
In case someone finds this in the future, I basically gave up. This scenario occurred on a VM in Azure against an SMB share. I ended up doing it as an alternative using a NFS share, which seemed to work. NO CLUE why the SMB share was blocking/locking/failing.
NuGet Product Used
dotnet.exe
Product Version
dotnet core 8
Worked before?
No response
Impact
It bothers me. A fix would be nice
Repro Steps & Context
Describe the bug No matter what I do I always get an error while trying to restore nuget on a single package file. A ton of other packages work successfully but this one always fails no matter what. If I run without the smb cache everything works fine but obviously much slower since I don't have any cache of files.
The build agent is a docker container on Ubuntu and I'm attaching an smb file share to /mnt/build-agent-share so that I can get nuget caching. I cannot mount a local folder to the docker image as I do not own the VM, its a shared "ephemeral" build agent designed to be killed off after every run.
I have attempted deleting the folder entirely and starting over, attempting to own the folder once its mounted.... Anyone have any ideas?
Verbose Logs