ci: pin nerdctl to v2.2.2 to fix smoke test failure

[Zephyrcf]

Overview

Fix TestTakeover/TestAPIHotUpgrade smoke test failure by pinning nerdctl to v2.2.2.

Related Issues

Related containerd/nerdctl#4583

Change Details

Since nerdctl v2.3.x, when connected to containerd >= 2.0.0, the image pull logic switches from the legacy client.Pull() to the client.Transfer() API , which requires unpack_config configured in containerd. There is no runtime flag to force the legacy client.Pull() path in v2.3.x.(SupportsFullTransferService)

The script misc/prepare.sh pulls the latest nerdctl version by default. After the upgrade, the smoke test failed with the error: unable to initialize unpacker: no unpack platforms defined: invalid argument
(CI failure)

When testing with nerdctl v2.3.x + containerd 2.x, adding these containerd config entries has been verified to resolve the issue and enable normal operation：

[[plugins.'io.containerd.transfer.v1.local'.unpack_config]]                                                                                                          
    platform = "linux/amd64"                                                                                                                                         
    snapshotter = "nydus"                                                                                                                                            
                                                                                                                                                                     
[proxy_plugins.nydus]                                                                                                                                                
    type = "snapshot"                                                                                                                                                
    address = "/run/containerd-nydus/containerd-nydus-grpc.sock"                                                                                                     
    [proxy_plugins.nydus.exports]                                                                                                                                    
        enable_remote_snapshot_annotations = "true"

Test Results

If you have any relevant screenshots or videos that can help illustrate your changes, please add them here.

Change Type

Please select the type of change your pull request relates to:

• Bug Fix
• Feature Addition
• Documentation Update
• Code Refactoring
• Performance Improvement
• Other (please describe)

Self-Checklist

Before submitting a pull request, please ensure you have completed the following:

• I have run a code style check and addressed any warnings/errors.
• I have added appropriate comments to my code (if applicable).
• I have updated the documentation (if applicable).
• I have written appropriate unit tests.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.68%. Comparing base (eb725d1) to head (ca13be2).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1947      +/-   ##
==========================================
+ Coverage   68.40%   72.68%   +4.27%     
==========================================
  Files         210      210              
  Lines       62747    62747              
  Branches    55524    55524              
==========================================
+ Hits        42921    45605    +2684     
+ Misses      18032    15083    -2949     
- Partials     1794     2059     +265     

see 29 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[BraveY]

Can we modify the configuration used to adapt to this latest version? I'm concerned that pinning the version may mask more issues over time.

[Zephyrcf]

Can we modify the configuration used to adapt to this latest version? I'm concerned that pinning the version may mask more issues over time.

Agreed. Let's update the config instead of pinning.

[BraveY]

LGTM