Skip to content
Open
Show file tree
Hide file tree
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
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,6 @@ import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL56 from "/
import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL69 from "/snippets/canton-docs/global-synchronizer_troubleshooting-guide_installation-issues_L69.mdx";
import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL78 from "/snippets/canton-docs/global-synchronizer_troubleshooting-guide_installation-issues_L78.mdx";
import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL92 from "/snippets/canton-docs/global-synchronizer_troubleshooting-guide_installation-issues_L92.mdx";
import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL102 from "/snippets/canton-docs/global-synchronizer_troubleshooting-guide_installation-issues_L102.mdx";
import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL118 from "/snippets/canton-docs/global-synchronizer_troubleshooting-guide_installation-issues_L118.mdx";
import CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL135 from "/snippets/canton-docs/global-synchronizer_troubleshooting-guide_installation-issues_L135.mdx";

Expand All @@ -23,14 +22,13 @@ Installation failures typically fall into three categories: container runtime is
If `docker compose up` fails with an image pull error:

```
Error response from daemon: pull access denied for digitalasset/canton-participant
Error response from daemon: pull access denied...
```

Possible causes:

- You are not logged in to the container registry. Run `docker login digitalasset-docker.jfrog.io` with your JFrog credentials.
- Your JFrog account does not have access to the required repositories. Request access through [support.digitalasset.com](https://support.digitalasset.com).
- A typo in the image tag. Verify the image name and version in your `docker-compose.yaml` or `.env` file against the release notes.
- Stale cached credentials from an old `docker login`.

### Resource Limits

Expand Down Expand Up @@ -97,14 +95,6 @@ If the main container never starts, an init container may be failing:

Init containers commonly fail due to database connectivity issues -- the PostgreSQL instance is unreachable or the credentials are wrong.

### Image Pull Secrets

Kubernetes needs explicit credentials to pull from private registries:

<CantonGlobalSynchronizerTroubleshootingGuideInstallationIssuesL102 />


Then reference `jfrog-creds` in your `validator-values.yaml` under `imagePullSecrets`.

## Network Issues

Expand Down

This file was deleted.