From af17d05c5a0bccbaa3d2dd3a9af14c369714929b Mon Sep 17 00:00:00 2001 From: karman <110832017+karman-docker@users.noreply.github.com> Date: Sat, 10 Jan 2026 19:51:16 +0000 Subject: [PATCH] Update troubleshooting guide with DOCKER_CONFIG note Added note about DOCKER_CONFIG environment variable affecting plugin detection. Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- content/manuals/ai/sandboxes/troubleshooting.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/manuals/ai/sandboxes/troubleshooting.md b/content/manuals/ai/sandboxes/troubleshooting.md index a59d3d4e9882..12ed06bd6067 100644 --- a/content/manuals/ai/sandboxes/troubleshooting.md +++ b/content/manuals/ai/sandboxes/troubleshooting.md @@ -16,7 +16,7 @@ This guide helps you resolve common issues when sandboxing Claude Code locally. When you run `docker sandbox`, you see an error saying the command doesn't exist. -This means the CLI plugin isn't installed or isn't in the correct location. To fix: +This means the CLI plugin isn't installed in the expected location. To fix: 1. Verify the plugin exists: @@ -26,7 +26,10 @@ This means the CLI plugin isn't installed or isn't in the correct location. To f The file should exist and be executable. -2. If using Docker Desktop, restart it to detect the plugin. +2. If the `DOCKER_CONFIG` environment variable is set to a path other than + `~/.docker`, unset it. + +3. Restart Docker Desktop to detect the plugin. ## "Experimental Features" needs to be enabled by your administrator