Skip to content

Commit bcea262

Browse files
committed
fix: add instructions how to set up dockercfg for public registries only
Add an additional example how the dockercfg file could look like if access to private registries is not required. This was raised as a question before so adding this to help customers not have to figure out everything on their own.
1 parent 45326c9 commit bcea262

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,12 @@ Both of these items must be provided from a Kubernetes secret. The secret must b
3838
}
3939
```
4040

41+
If access to private registries is not needed, the `dockercfg.json` file contents should look like this:
42+
43+
```json
44+
{}
45+
```
46+
4147
2. Locate your Snyk Integration ID from the Snyk Integrations page (navigate to https://app.snyk.io/org/YOUR-ORGANIZATION-NAME/manage/integrations/kubernetes) and copy it.
4248
The Snyk Integration ID is a UUID and looks similar to the following:
4349
```

snyk-monitor/README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,12 @@ Both of these items must be provided by a Kubernetes secret. The secret must be
3333
}
3434
```
3535

36+
If access to private registries is not needed, the `dockercfg.json` file contents should look like this:
37+
38+
```json
39+
{}
40+
```
41+
3642
2. Locate your Snyk Integration ID from the Snyk Integrations page (navigate to https://app.snyk.io/org/YOUR-ORGANIZATION-NAME/manage/integrations/kubernetes) and copy it. The Snyk Integration ID looks similar to the following:
3743
```
3844
abcd1234-abcd-1234-abcd-1234abcd1234

0 commit comments

Comments
 (0)