From f9694f77fe8094fe900d761455c0a2e1067999cd Mon Sep 17 00:00:00 2001 From: Ahmad Hassan Date: Fri, 15 Aug 2025 11:48:27 +0500 Subject: [PATCH] Improve the documentation around docker and ghcr image registry configuration Signed-off-by: Ahmad Hassan --- .../inspecting-the-cluster.rst | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/how-to/troubleshooting/inspecting-the-cluster.rst b/how-to/troubleshooting/inspecting-the-cluster.rst index 57a96ef..fcbf8d9 100644 --- a/how-to/troubleshooting/inspecting-the-cluster.rst +++ b/how-to/troubleshooting/inspecting-the-cluster.rst @@ -235,3 +235,29 @@ the lock timestamp is. Ensure that there are no administrative operations underway in the deployment when unlocking a Terraform plan. Otherwise, the deployment’s integrity can be compromised. + +Docker registry timeouts +-------------------------- + +While bootstrapping the controller on Kubernetes, the Sunbeam default +bootstrap configuration uses `docker.io` for pulling images. If the pods +fail to pull images, use the following `ghcr.io` registry configuration +in the custom manifest file, as shown below: + +:: + + core: + software: + juju: + bootstrap_args: + - --config + - caas-image-repo=ghcr.io/juju + +.. caution:: + Ensure that the above configuration is added to the full manifest. + +Use the above manifest as: + +:: + + sunbeam cluster bootstrap --manifest