结论

  msb 项目在腾讯云上无法正常运行。因为 msb 需要嵌套虚拟化，但是腾讯云上不支持嵌套虚拟化。

msb 介绍

  msb 是一个轻量级的沙箱运行时，支持嵌套虚拟化，可以运行在任何支持嵌套虚拟化的平台上。 项目地址：https://github.com/microsandbox/microsandbox

腾讯云

TencentOS Server release 3.3 (Final)

1
2

# msb
msb: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

缺少 libssl3 库，dnf install openssl3 解决。

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

[root@VM-220-7-tencentos ~]# msb
msb: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by msb)
msb: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by msb)
msb: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by msb)
msb: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by msb)
msb: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by msb)
msb: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /root/.local/lib/libkrun.so.1)
msb: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by /root/.local/lib/libkrun.so.1)
[root@VM-220-7-tencentos ~]# cat /etc/redhat-release 
TencentOS Server release 3.3 (Final)

国内腾讯云上，msb 无法拉取镜像，也不能使用加速源，使用东京实例测试。

1
2
3
4
5
6
7
8
9

[root@VM-220-29-tencentos ~]# msb pull alpine
Error: http middleware error: Request error: error sending request for url (https://auth.docker.io/token?service=registry.docker.io&scope=repository%3Alibrary%2Falpine%3Apull)

Caused by:
    1: Request error: error sending request for url (https://auth.docker.io/token?service=registry.docker.io&scope=repository%3Alibrary%2Falpine%3Apull)
    2: error sending request for url (https://auth.docker.io/token?service=registry.docker.io&scope=repository%3Alibrary%2Falpine%3Apull)
    3: client error (Connect)
    4: tcp connect error: Connection timed out (os error 110)
    5: Connection timed out (os error 110)

Ubuntu 22.04 (Jammy Jellyfish)

无法嵌套虚拟化，创建 kvm 对象失败。

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

# msb exe alpine
✓ Initialize .menv directory
✓ Create default config file
thread '<unnamed>' panicked at src/vmm/src/linux/vstate.rs:417:30:
Error creating the Kvm object: Error(2)
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: vmm::linux::vstate::KvmContext::new
   4: krun_start_enter
   5: microsandbox_core::vm::vm::MicroVm::start
   6: msbrun::main::{{closure}}
   7: tokio::runtime:🏞:CachedParkThread::block_on
   8: tokio::runtime::context::runtime::enter_runtime
   9: tokio::runtime::runtime::Runtime::block_on
  10: msbrun::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

thread '<unnamed>' panicked at library/core/src/panicking.rs:218:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7fd4c0d217cc - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h6d42cc84fc840290
   1:     0x7fd4c0bee0b3 - core::fmt::write::h5af61a909e3ec64d
   2:     0x7fd4c0d20d52 - std::io::Write::write_fmt::h5a7b54aa6e4a315d
   3:     0x7fd4c0d214c3 - std::sys::backtrace::BacktraceLock::print::h555579e7396c26ac
   4:     0x7fd4c0d20b27 - std::panicking::rust_panic_with_hook::h541791bcc774ef34
   5:     0x7fd4c0d4ef55 - std::panicking::begin_panic_handler::{{closure}}::h6479a2f0137c7d19
   6:     0x7fd4c0d4eee9 - std::sys::backtrace::__rust_end_short_backtrace::ha04e7c0fc61ded91
   7:     0x7fd4c0d4f4cc - rust_begin_unwind
   8:     0x7fd4c0b99cac - core::panicking::panic_nounwind_fmt::h6a24774852878975
   9:     0x7fd4c0b99d0c - core::panicking::panic_nounwind::hbbbf5b15de703440
  10:     0x7fd4c0b99cbc - core::panicking::panic_cannot_unwind::h8c0d27499c4c90fa
  11:     0x7fd4c0bb5a4e - krun_start_enter
  12:     0x5571f4b848bd - microsandbox_core::vm::vm::MicroVm::start::h5aba1754a3f4c051
  13:     0x5571f4a99bd7 - msbrun::main::{{closure}}::h285e41ad8a1d686e
  14:     0x5571f4a89288 - tokio::runtime:🏞:CachedParkThread::block_on::hdae61bb89cbac529
  15:     0x5571f4ae712c - tokio::runtime::context::runtime::enter_runtime::h74d6b37c42e9139f
  16:     0x5571f4af6b5c - tokio::runtime::runtime::Runtime::block_on::h1078d612bdfd9823
  17:     0x5571f4aed179 - msbrun::main::h826b12470ada077f
  18:     0x5571f4afc7f3 - std::sys::backtrace::__rust_begin_short_backtrace::he0cc31bfd45d0267
  19:     0x5571f4ade19d - std::rt::lang_start::{{closure}}::h620ace340a1af2a9
  20:     0x5571f4f5e4c0 - std::rt::lang_start_internal::h15895544e2012228
  21:     0x5571f4aed255 - main
  22:     0x7fd4c037dd90 - <unknown>
  23:     0x7fd4c037de40 - __libc_start_main
  24:     0x5571f4a60a61 - _start
  25:                0x0 - <unknown>
thread caused non-unwinding panic. aborting.
2025-07-24T22:19:03.428667Z ERROR microsandbox_utils::runtime::supervisor: child process 3794119 exited with status: ExitStatus(unix_wait_status(134))