chore(deps): update module github.com/containerd/stargz-snapshotter/estargz to v0.18.1

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/containerd/stargz-snapshotter/estargz	v0.16.3 -> v0.18.1

---

Release Notes

containerd/stargz-snapshotter (github.com/containerd/stargz-snapshotter/estargz)

v0.18.1

Compare Source

Notable Changes

• Avoid repeated decompression and further utilize the --GH option to speed up conversion (#​2145), thanks to @​escapefreeg
• Improved sortEntries performance (#​2153), thanks to @​wswsmao

v0.18.0

Compare Source

Notable Changes

• Fixed restoring error of snapshots on unexpected restart of stargz snapshotter (#​2091, #​2092), thanks to @​wswsmao
• Added FadvDontNeed option to reduce pagecache consumption in stargz snapshotter (#​2095), thanks to @​wswsmao
• Removed testing dependency from code outside tests (#​2098), thanks to @​rosstimothy
• Added all option for the ctr-remote's --gpus flag (#​2102, #​2118), thanks to @​wswsmao
• Added --prefetch-list flag to ctr-remote (#​2113, #​2148), thanks to @​wswsmao
• Enabled deduplication in ImageRecorder.Record (#​2116), thanks to @​wswsmao
• Fixed potential data race in nativeconverter/estargz (#​2133), thanks to @​escapefreeg
• Added support of decompression helpers in ctr-remote for better conversion speed (#​2117), thanks to @​escapefreeg
• Improved logging behaviour in fusemanager (#​2135), thanks to @​mmonaco
• Fixed to preserve normal snapshots during cleanup in stargz snapshotter (#​2127), thanks to @​ChengyuZhu6
• Fixed lazy pulling failure on images with empty layers (#​2137)
• Fixed stargz snapshotter to run without depending on fusermount by default (#​2146)
• Enabled ctr-remote to capture early file access (#​2129), thanks to @​wswsmao
• Refactors and document fixes (#​2112, #​2150), thanks to @​wswsmao

v0.17.0

Compare Source

Notable Changes

• New features
  • Added support for FUSE passthourgh (#​1868, #​1870, #​1874, #​1876, #​1881, #​1923, #​1987, #​2012, #​2045, #​2068), thanks to @​wswsmao
  • Added support for detaching FUSE server as a separated processs (FUSE manager), thanks to @​wswsmao (#​1892, #​1912, #​1905) and @​ilyee (#​1892)
  • Expanded support for graceful restarting of Stargz Snapshotter (#​2077)
  • Added arm64 KIND node image (ghcr.io/containerd/stargz-snapshotter:0.17.0-kind) (#​1983)
• Fixes and changes
  • Set maximum filename length to 255 bytes (#​2024), thanks to @​wswsmao
  • Fixed EOPNOTSUPP issue on getdents64 (#​2063), thanks to @​wswsmao
  • Fixed TTLCache failed to release resources on exit (#​2076)
  • Fixed the configuration and docs to prevent GC failures in CRI plugin (#​1893)
  • Refactored blob manipulation logic to make it more modular (#​1955), thanks to @​ChengyuZhu6
  • Fix zstd:chunked converter error on duplicated blobs (#​1885), thanks to @​apostasie
• Document updates
  • Added docs about how to use Stargz Snapshotter on Lima (#​1967)
  • Added docs about how to use Stargz Snapshotter with Transfer Service (#​2084)
  • Improved legibility in docs/overview.md (#​2061), thanks to @​soulshake
• CI updates
  • Added tests for wider configrations (FUSE passthrough and FUSE manager) (#​2074, #​2083, #​1914)
  • Fixed dependabot's configuration to avoid CI failures in gomod PRs (#​1920, #​1941), thanks to @​djdongjin
  • Bump up containerd/project-checks to v1.2.2 (#​2004), thanks to @​wswsmao
• Dependencies
  • Replace harshicorp/multierror with errors.Join (#​1921), thanks to @​djdongjin
  • Bump up Kubernetes to v1.33 (#​2078)
  • go.mod dependency updates (#​1936, #​1942), thanks to @​thaJeztah

For other changes, refer to the full diff: containerd/stargz-snapshotter@v0.16.3...v0.17.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[red-hat-konflux]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 3 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.23.3 -> 1.24.0
go (toolchain)	1.23.9 -> 1.24.6
github.com/klauspost/compress	v1.18.0 -> v1.18.1
github.com/vbatts/tar-split	v0.12.1 -> v0.12.2
golang.org/x/sync	v0.13.0 -> v0.17.0

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign adambkaplan for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.