From 89f799fa613778fadd2f0b8b6713ca75ca78431e Mon Sep 17 00:00:00 2001
From: Peter Holloway <peter.holloway@diamond.ac.uk>
Date: Thu, 23 Oct 2025 16:12:52 +0100
Subject: [PATCH] Use shared volume for devcontainer uv cache

Instead of mounting the user's local cache. For the first use this will
be slower (if the user has previously used uv) but using a separate
volume means links within the cache referring to devcontainer locations
will not interfere with uv being run from outside the container.

Using a named volume means devcontainers for multiple projects can share
the same cache.
---
 .devcontainer/devcontainer.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index de182095..693beaf9 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -56,9 +56,9 @@
         },
         // Keep a persistent cross container cache for uv
         {
-            "source": "${localEnv:HOME}/.cache/uv",
+            "source": "persistent-uv-cache",
             "target": "/root/.cache/uv",
-            "type": "bind"
+            "type": "volume"
         },
         // Use a volume mount for the uv venv so it is local to the container
         {