Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions how-to/troubleshooting/inspecting-the-cluster.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think inspecting the cluster is the right place for such workarounds.

--------------------------

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 <name-of-the-file>