docs/userns: Clarify containerd 1.7 limitations
Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>
This commit is contained in:
parent
e379082000
commit
d008d64a8f
@ -74,9 +74,9 @@ Different containerd versions have different limitations too, those are highligh
|
|||||||
### containerd 1.7
|
### containerd 1.7
|
||||||
|
|
||||||
One limitation present in containerd 1.7 is that it needs to change the ownership of every file and
|
One limitation present in containerd 1.7 is that it needs to change the ownership of every file and
|
||||||
directory inside the container image, during Pod startup. This means it has a storage overhead (the
|
directory inside the container image, during Pod startup. This means it has a storage overhead, as
|
||||||
size of the container image is duplicated each time a pod is created) and can significantly impact
|
**the size of the container image is duplicated each time a pod is created**, and can significantly
|
||||||
the container startup latency.
|
impact the container startup latency, as doing such a copy takes time too.
|
||||||
|
|
||||||
You can mitigate this limitation by switching `/sys/module/overlay/parameters/metacopy` to `Y`. This
|
You can mitigate this limitation by switching `/sys/module/overlay/parameters/metacopy` to `Y`. This
|
||||||
will significantly reduce the storage and performance overhead, as only the inode for each file of
|
will significantly reduce the storage and performance overhead, as only the inode for each file of
|
||||||
|
Loading…
Reference in New Issue
Block a user