Skip to content

.NET Core

Example configuration

      - local: .
        container: /code
        options: cached
      - type: cache
        name: nuget-cache
        container: /root/.nuget/packages

      # Repeat this cache for each project in your codebase:
      - type: cache
        name: project1-obj
        container: /code/project1/obj

    working_directory: /code

Caching dependencies


Mount a cache into your container for downloaded NuGet packages, otherwise you'll have to download and compile your dependencies every time the build runs

By default, dotnet stores downloaded NuGet packages in ~/.nuget/packages. However, because batect destroys all of your containers once the task finishes, this directory is lost at the end of every task run - which means that dotnet will have to download all of your dependencies again next time you run the task, significantly slowing down the build.

The solution to this is to mount a cache that persists between builds into the container at ~/.nuget/packages, so that these downloaded dependencies are persisted between builds.

Note that you can't use ~ in the container path for a volume mount:

Caching build output


Mount a cache into your container the obj directory for each project in your codebase, otherwise you'll experience poor performance on macOS and Windows, and issues with some IDEs.

The obj directory is used to store intermediate build output. However, when running on macOS and Windows, Docker exhibits poor I/O performance for directories mounted from the macOS or Windows host, as discussed in the section on caches.

Furthermore, the obj directory contains files that include the absolute path to the NuGet packages in your project, which are only correct in the context of the container. This can cause issues for some IDEs (including Rider) that rely on these files to show code completion information for dependencies.

The solution to this is to mount a cache that persists between builds into your container for each project's obj directory.