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/overview.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,12 @@ Remote snapshots are mounted using FUSE, and its filesystem processes are attach
108
108
109
109
To avoid this, we use a fuse daemon called the fuse manager to handle filesystem processes. The fuse manager is responsible for mounting and unmounting remote snapshotters. Its process is detached from the stargz snapshotter main process to an independent one in a shim-like way during the snapshotter's startup. This design ensures that the restart of the snapshotter won't affect the filesystem processes it manages, keeping mountpoints and running containers available during the restart. However, it is important to note that the restart of the fuse manager itself triggers a remount, so it is recommended to keep the fuse manager running in a good state.
110
110
111
-
You can enable the fuse manager by adding the flag `--detach-fuse-manager=true` to the stargz snapshotter.
111
+
You can enable the fuse manager by adding the following configuration.
112
+
113
+
```toml
114
+
[fusem_anager]
115
+
enable = true
116
+
```
112
117
113
118
## Killing and restarting Stargz Snapshotter
114
119
@@ -173,13 +178,23 @@ The snapshotter acquires registry creds by scanning requests.
173
178
174
179
You must specify `--image-service-endpoint=unix:///run/containerd-stargz-grpc/containerd-stargz-grpc.sock` option to kubelet.
175
180
181
+
You can specify the backing image service's socket using `image_service_path`.
182
+
The default is the containerd's socket (`/run/containerd/containerd.sock`).
183
+
176
184
```toml
177
185
# Stargz Snapshotter proxies CRI Image Service into containerd socket.
The default path where containerd-stargz-grpc serves the CRI Image Service API is `unix:///run/containerd-stargz-grpc/containerd-stargz-grpc.sock`.
192
+
You can also change this path using `listen_path` field.
193
+
194
+
> Note that if you enabled the FUSE manager and CRI-based authentication together, `listen_path` is a mandatory field with some caveats:
195
+
> - This path must be different from the FUSE manager's socket path (`/run/containerd-stargz-grpc/fuse-manager.sock`) because they have different lifecycle. Specifically, the CRI socket is recreted on each reload of the configuration to the FUSE manager.
196
+
> - containerd-stargz-grpc's socket path (`/run/containerd-stargz-grpc/containerd-stargz-grpc.sock`) can't be used as `listen_path` because the CRI socket is served by the FUSE manager process (not containerd-stargz-grpc process).
197
+
183
198
#### kubeconfig-based authentication
184
199
185
200
This is another way to enable lazy pulling of private images on Kubernetes.
0 commit comments