You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/kubernetes.md
+24-2Lines changed: 24 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,17 @@ This document explains how to configure SOCI on Kubernetes. For a hands on examp
11
11
## Configuration
12
12
13
13
SOCI on kubernetes requires two pieces of configuration:
14
+
14
15
1)[Containerd Configuration](#containerd-configuration) to launch containers with SOCI
15
16
2)[Registry Authentication Configuration](#registry-authentication-configuration) so that SOCI can pull images from non-public container registries
16
17
17
18
### Containerd configuration
18
19
19
-
To configure containerd to launch containers with SOCI, add the following snippet to the containerd config. The config is located at `/etc/containerd/config.toml` by default.
20
+
To configure containerd to launch containers with SOCI, add the following snippet to the containerd config. The config is located at `/etc/containerd/config.toml` by default.
` snapshotter = "soci"` tells containerd to use SOCI by default. This name must match the proxy_plugin name. (this is required. See [Limitations](#limitations))
48
51
` disable_snapshot_annotations = false` tells containerd to send lazy loading information to the SOCI snapshotter
# This line is required for containerd to send information about how to lazily load the image to the snapshotter
65
+
disable_snapshot_annotations = false
66
+
```
67
+
68
+
> **NOTE**
69
+
>
70
+
> The change from the containerd 1.x configuration is the header for kubernetes-specific configuration.
71
+
50
72
### Registry Authentication Configuration
51
73
52
74
The SOCI snapshotter lazily pulls image content outside of the normal image pull context. As a result, it must be independently configured to receive credentials to access non-public container registries.
0 commit comments