Skip to content

Commit 1abe0a8

Browse files
committed
docs: clarify partial vs lazy image pulling
The performance tutorial calls Podman's zstd:chunked / eStargz support "lazy pulling", which isn't accurate. By itself Podman only does partial pulling: it skips layer content it already has, but the image is still fully pulled before a container runs. Real lazy pulling, where the image is mounted before the download finishes, needs an external snapshotter such as stargz-snapshotter. Rename the section to "partial pulling" and add a sentence spelling out the difference, as @giuseppe suggested on the issue. Fixes: #24947 Signed-off-by: Grzegorz Szczepanczyk <g.szczepanczyk@getprintbox.com>
1 parent df12c98 commit 1abe0a8

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

docs/tutorials/performance.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -180,21 +180,23 @@ $ podman info -f '{{.Host.RootlessNetworkCmd}}'
180180
pasta
181181
```
182182

183-
### Lazy pulling of container images
183+
### Partial pulling of container images
184184

185-
Podman supports lazy pulling for the following container image formats:
185+
Podman supports partial pulling for the following container image formats:
186186

187187
* __zstd:chunked__
188188

189189
* __eStargz__
190190

191191
__zstd:chunked__ has better performance than __eStargz__.
192192

193+
Partial pulling downloads only the layer contents that are missing locally, but the image is still fully pulled before its containers run. Lazy pulling, where the image is mounted before it is fully downloaded, is out of scope for Podman itself and requires an additional snapshotter such as the [stargz-snapshotter](https://github.com/containerd/stargz-snapshotter) configured as an additional layer store.
194+
193195
See the article [_Pull container images faster with partial pulls_](https://www.redhat.com/sysadmin/faster-container-image-pulls) by Giuseppe Scrivano and Dan Walsh.
194196

195197
### Choosing a host file system
196198

197-
Lazy pulling of container images can run more efficiently when the file system has reflink support. The file systems XFS and BTRFS have reflink support.
199+
Partial pulling of container images can run more efficiently when the file system has reflink support. The file systems XFS and BTRFS have reflink support.
198200

199201
### Option --log-driver
200202

0 commit comments

Comments
 (0)