.NET SDK and Docker Dev Containers: NuGet Cache Persistence

Development Environment Repeatability

Implementing a repeatable development environment using .NET Dev Containers involves pinning the SDK version within a .devcontainer.json configuration and a corresponding Dockerfile. This ensures that all contributors utilize an identical runtime and build toolchain regardless of the host operating system.

Host-Container Boundary Constraints

While bind mounts allow source code to synchronize between the host and the container, the ~/.nuget/packages folder typically resides within the container's ephemeral file system. This results in redundant package restorations every time the container is rebuilt or reset, impacting build performance.

There is a design trade-off between maintaining a completely isolated environment and optimizing restoration speeds via named volumes or host-path mapping, especially when considering architecture differences between x64 and ARM64 hosts.

• How can the NuGet package cache be persisted across container rebuilds without compromising the environment's repeatability?
• What is the recommended strategy for mapping the NuGet cache to a host volume while avoiding permission conflicts across different OS architectures?