BUG: sealos run hangs at syncing images to 5050 registry

[szediktam]

Sealos Version

5.0.1

How to reproduce the bug?

1. sealos run a cluserimage ,
   /usr/local/bin/sealos run --debug -f cert-manager --env TIMEOUT=60s xxxxx
2. sealos print the output
   .................
   2025-12-23T20:34:46 ^[[34minfo^[[0m ^[[34m trying default http mode to sync images to hosts [xxxxx:22]^[[0m^M
   2025-12-23T20:34:46 ^[[35mdebug^[[0m ^[[35mchecking if endpoint http://xxxxx:5050 is alive^[[0m^M
   2025-12-23T20:34:46 ^[[35mdebug^[[0m ^[[35mrunning temporary registry on host xxxxx:22^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35mhttp endpoint http://xxxxxx:5050 is alive^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35mchecking if endpoint http://127.0.0.1:32769 is alive^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35mchecking if endpoint http://127.0.0.1:32769 is alive^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35m syncing repos [{jetstack/cert-manager-cainjector 0 false false false} {jetstack/cert-manager-controller 0 false false false} {jetstack/cert-manager-webhook 0 false false false}] from 127.0.0.1:32769 to 70.189.46.216:5050^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35msyncing repos [{jetstack/cert-manager-cainjector 0 false false false} {jetstack/cert-manager-controller 0 false false false} {jetstack/cert-manager-webhook 0 false false false}] from 127.0.0.1:32769 to 70.189.46.216:5050^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-cainjector:v1.13.2 with selection 1^[[0m^M
   2025-12-23T20:34:47 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-cainjector:v1.13.2 with selection 1^[[0m^M
   2025-12-23T20:34:48 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-cainjector:v1.13.2 with selection 0^[[0m^M
   2025-12-23T20:34:48 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-cainjector:v1.13.2 with selection 0^[[0m^M
   2025-12-23T20:34:48 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-controller:v1.13.2 with selection 1^[[0m^M
   2025-12-23T20:34:48 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-controller:v1.13.2 with selection 1^[[0m^M
   2025-12-23T20:34:49 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-controller:v1.13.2 with selection 0^[[0m^M
   2025-12-23T20:34:49 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-controller:v1.13.2 with selection 0^[[0m^M
   2025-12-23T20:34:49 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-webhook:v1.13.2 with selection 1^[[0m^M
   2025-12-23T20:34:49 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-webhook:v1.13.2 with selection 1^[[0m^M
   2025-12-23T20:34:49 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-webhook:v1.13.2 with selection 0^[[0m^M
   2025-12-23T20:34:49 ^[[35mdebug^[[0m ^[[35msyncing xxxxx:5050/jetstack/cert-manager-webhook:v1.13.2 with selection 0^[[0m
3. sealos hangs here

What is the expected behavior?

sealos run successfully.

What do you see instead?

sealos run hangs at syncing images to 5050 registry.

Operating environment

- Sealos version:
   5.0.1
- Docker version:
  25.0.5
- Kubernetes version:
  1.27.0
- Operating system:
   Ubuntu 22.04
- Runtime environment:
- Cluster size:
- Additional information:

Additional information

No response

[szediktam]

@cuisongliu @fengxsong Is this a bug of sealos?
This problem still exists in the latest version.