Skip to content

snapshot: restore remote mounts on demand after restart - #2359

Open
wxx213 wants to merge 1 commit into
containerd:mainfrom
wxx213:fix_invalid_mount_recover
Open

snapshot: restore remote mounts on demand after restart#2359
wxx213 wants to merge 1 commit into
containerd:mainfrom
wxx213:fix_invalid_mount_recover

Conversation

@wxx213

@wxx213 wxx213 commented Aug 3, 2026

Copy link
Copy Markdown

Add lazy_restore_on_restart to skip remote resolution and FUSE mount restoration during snapshotter startup.

When an unregistered remote layer is first used, restore its mount from the snapshot labels. Coalesce concurrent requests for the same mountpoint and support both in-process and fuse-manager modes.

This allows the snapshotter to start while the registry is unavailable.

@wxx213
wxx213 force-pushed the fix_invalid_mount_recover branch from 7de887f to 0481f60 Compare August 4, 2026 04:38
@ktock

ktock commented Aug 7, 2026

Copy link
Copy Markdown
Member

This allows the snapshotter to start while the registry is unavailable.

Can you elaborate this? Why is the registry unavailable during the snapshotter startup?

@wxx213

wxx213 commented Aug 7, 2026

Copy link
Copy Markdown
Author

elaborate

We deployed our image cached registry in cluster by k8s service,most of our application images use it but except like cilium pods.

On the host reboot,stargz snapshotter cannot connect the registry by service ip to recover remote snapshotters when cilium pod is not ready. So we need the lazy snapshotter recover feature like this.

Add lazy_restore_on_restart to skip remote resolution and FUSE mount
restoration during snapshotter startup.

When an unregistered remote layer is first used, restore its mount from
the snapshot labels. Coalesce concurrent requests for the same
mountpoint and support both in-process and fuse-manager modes.

This allows the snapshotter to start while the registry is unavailable.

Signed-off-by: Wang Xingxing <wangxingxing@siliconflow.cn>
@wxx213
wxx213 force-pushed the fix_invalid_mount_recover branch from 0481f60 to 2302135 Compare August 19, 2026 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants