NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #281 by repository stars
Latest stable
v0.7.3
Last release 1 months ago
14 Oct 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 16 of 16 stable releases
Nothing withdrawn
no release was ever pulled
7 months old
447 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
Nothing published for this version
32 commits from 15 contributors.
32 commits from 15 contributors.
Sandboxes can now be created with an E2B-compatible mcp parameter, which starts an MCP (Model Context Protocol) gateway inside the sandbox:
examples/mcp-gateway.no more resource (#1909).cubemastercli tpl ls now support paging (limit / offset).cubemastercli accumulating zombie processes; a one-time pod restart clears existing ones (#1860).Watcher closing twice under concurrency (#1405).32 个提交,来自 15 位贡献者。
创建沙箱时支持传入与 E2B 兼容的 mcp 参数,在沙箱内启动 MCP(Model Context Protocol)网关:
examples/mcp-gateway 提供了默认参考实现no more resource 的问题(#1909)。cubemastercli tpl ls 同时支持分页(limit / offset)。cubemastercli 僵尸进程不断堆积的问题,存量部署重启一次 Pod 即可清理(#1860)。Watcher 并发场景下重复关闭问题(#1405)。Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
CubeSandbox 0.7.2 introduces 3 major features along with multiple enhancements and bug fixes. 56 commits from 29 contributors.
CubeSandbox 0.7.2 introduces 3 major features along with multiple enhancements and bug fixes. 56 commits from 29 contributors.
Sandboxes restored cross-node on the S3 backend read disk data from S3 on demand; this release optimizes that read path systematically:
New JuiceFS storage plugin: sandboxes can mount a JuiceFS filesystem as a persistent volume, with full POSIX semantics.
Idle memory inside sandboxes is reclaimed back to the host: node memory usage falls back dynamically with the real usage of the sandboxes, so a single node can host more sandboxes.
sandbox.connect supports a timeout parameter (#1352).hostNetworkChangeAck); fresh installs are unaffected.envd Connect RPC (#1786).run_code (E2B-compatible code-interpreter interface) can now read environment variables injected at sandbox creation (#1323), matching the behavior of commands.run; the new sandbox-code example image is required.BUILT with database connection timeouts (#1802).end_at=0) in Info / List queries (#1801).Could not restore GICv3ITS state): the vgic state save was incorrectly optimized to all zeros by the compiler (#1658).cubeNode.network.mtu (#1674).CUBE_SANDBOX_CUBE_EGRESS_IMAGE environment variable not being updated in .one-click.env for one-click deployments (#1788).docker-ce (#1789).CubeSandbox 0.7.2 引入了 3 个核心特性以及多个功能增强与问题修复。共计 56 个提交,来自 29 位贡献者。
S3 后端跨机恢复的沙箱,磁盘数据按需从 S3 拉取;本版本对这条读路径做了系统性优化:
新增 JuiceFS 存储插件:沙箱可挂载 JuiceFS 文件系统作为持久卷,具备完整 POSIX 语义。
沙箱内的空闲内存自动回收到宿主机:节点内存占用随沙箱实际用量动态回落,单节点可承载更多沙箱。
sandbox.connect 支持 timeout 参数(#1352)。hostNetworkChangeAck),全新安装不受影响。envd Connect RPC(#1786)。run_code(E2B 兼容代码解释器接口)现在也能读到创建沙箱时注入的环境变量(#1323),与 commands.run 行为一致;需使用新增的 sandbox-code 示例镜像。BUILT 状态,数据库连接超时的竞态问题(#1802)。end_at=0)的问题(#1801)。cubeNode.network.mtu 固定(#1674)。CUBE_SANDBOX_CUBE_EGRESS_IMAGE 环境变量未正确更新到 .one-click.env 的问题(#1788)。docker-ce(#1789)。SQLSTATE 精确分类(#1724)。cubebench CPU 拓扑报告的兼容性问题(#1757)。Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixed the Web UI runtime config page showing deprecated settings (#1573).
CubeSandbox 0.7.1 introduces 1 major feature along with multiple enhancements and bug fixes. 70 commits from 24 contributors.
CUBE_DATABASE_DRIVER and connect to a self-managed database instance.[cow.s3] enable = true (or ONE_CLICK_ENABLE_S3LVOL=1 for one-click deploy); it is disabled by default. Also fixes the switch not taking effect during one-click upgrades. Upgrade note: nodes that were using S3 without an explicit setting must enable it after upgrade.redis.db applies to CubeMaster / CubeProxy / CLM, so multiple clusters sharing one Redis instance can isolate logical databases per cluster.tpl delete accepts multiple template IDs in one call.NEVER_TIMEOUT) being immediately treated as expired (#1401).cubecli logs for sandboxes created from a template (#1616).global.imageRegistry overwriting explicitly configured private / third-party registry addresses (#1605).info) not taking effect and falling back to DEBUG (#1597).0 or NEVER_TIMEOUT (#1485).version subcommand being unavailable (#1596).version producing no output by default (#1657).CubeSandbox 0.7.1 引入了 1 个核心特性以及多个功能增强与问题修复。共计 70 个提交,来自 24 位贡献者。
CUBE_DATABASE_DRIVER 选择 MySQL / PostgreSQL,接入自建数据库实例。[cow.s3] enable = true(一键部署用 ONE_CLICK_ENABLE_S3LVOL=1),默认关闭;同时修复一键部署升级时该开关不生效的问题。升级注意:此前未显式配置但实际在使用 S3 的节点,升级后需显式开启。redis.db,统一作用于 CubeMaster / CubeProxy / CLM;多套集群共享同一 Redis 时可按集群隔离逻辑库。tpl delete 支持一次传入多个模板 ID。NEVER_TIMEOUT)后被立即判定为已过期的问题(#1401)。cubecli logs 无输出)的问题(#1616)。global.imageRegistry 误改写显式指定的私有 / 第三方镜像仓库地址的问题(#1605)。info)时不生效、回落到 DEBUG 的问题(#1597)。0 或 NEVER_TIMEOUT 超时后请求永不返回的问题(#1485)。version 子命令不可用的问题(#1596)。version 命令默认无输出的问题(#1657)。Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
CubeSandbox 0.7.0 introduces 4 major features along with multiple enhancements and bug fixes. 239 commits from 57 contributors.
CubeSandbox 0.7.0 introduces 4 major features along with multiple enhancements and bug fixes. 239 commits from 57 contributors.
With an S3 backend, sandboxes support pause/resume across nodes as well as creating sandboxes from snapshots. This feature is currently in preview.
Architecturally, operations capabilities are split out of CubeMaster. Node management logic now lives in CubeOps, which supports multi-replica deployment and ships the cubeopscli tool.
volumeMounts, bringing all three languages to parity.Files.ForUser isolates file access by user identity.Sandbox.setTimeout(timeout) supports NEVER_TIMEOUT.Sandbox.create(distribution_scope=...) explicitly specifies the nodes/zones a sandbox can be placed on.Authorization header explicitly set by the caller (including lowercase variants) is no longer overridden by the SDK's default apiKey.kernel-release-* / guest-image-* releases.CubeSandbox 0.7.0 引入了4个核心特性以及多个功能增强与问题修复。共计 239 个提交,来自 57 位贡献者。
基于S3后端存储支持跨机的pause/resume以及基于snapshot创建沙箱,该功能目前是预览版本。
在架构上,将运维能力从CubeMaster中分离。把节点管理逻辑独立到CubeOps中,支持多副本部署,提供cubeopscli工具。
volumeMounts 挂载,三语言能力拉齐。Files.ForUser 按用户身份隔离文件访问。Sandbox.setTimeout(timeout) 支持 NEVER_TIMEOUT。Sandbox.create(distribution_scope=...) 显式指定沙箱可放置的节点/区域。Authorization(含小写形式)不再被 SDK 默认 apiKey 覆盖。kernel-release-* / guest-image-* Release 拉取固定版本This release has been tracked through the 0.7.0 project.
Highlights for cloud-hypervisor version 0.7.0 include:
Further to our effort to support modifying a running guest we now support
hotplug and unplug of the following virtio backed devices: block, network,
pmem, virtio-fs and vsock. This functionality is available on the (default) PCI
based transport and is exposed through the HTTP API. The ch-remote utility
provides a CLI for adding or removing these device types after the VM has
booted. User can use the id parameter on the devices to choose names for
devices to ease their removal.
libc SupportCloud Hypervisor can now be compiled with the musl C library and this release
contains a static binary compiled using that toolchain.
vhost-user BackendsThe vhost-user backends for network and block support that are shipped by
Cloud Hypervisor have been enhanced to support multiple threads and queues to
improve throughput. These backends are used automatically if vhost_user=true
is passed when the devices are created.
By passing the --initramfs command line option the user can specify a file to
be loaded into the guest memory to be used as the kernel initial filesystem.
This is usually used to allow the loading of drivers needed to be able to
access the real root filesystem but it can also be used standalone for a very
minimal image.
virtio-memAs well as supporting ACPI based hotplug Cloud Hypervisor now supports using
the virtio-mem hotplug alternative. This can be controlled by the
hotplug_method parameter on the --memory command line option. It currently
requires kernel patches to be able to support it.
Seccomp SandboxingCloud Hypervisor now has support for restricting the system calls that the
process can use via the seccomp security API. This on by default and is
controlled by the --seccomp command line option.
With the release of Ubuntu 20.04 we have added that to the list of supported distributions and is part of our regular testing programme.
This is non exhaustive list of HTTP API and command line changes
id fields added for devices to allow them to be named to ease removal.
If no name is specified the VMM chooses one.--memory's shared and hugepages controls for determining backing
memory instead of providing a path.--vsock parameter only takes one device as the Linux kernel only
supports a single Vsock device. The REST API has removed the vector for this
option and replaced it with a single optional field.vhost-user backed
device.ch-remote has added add-disk, add-fs, add-net, add-pmem and
add-vsock subcommands. For removal remove-device is used. The REST API
has appropriate new HTTP endpoints too.size with --pmem is no longer required and instead the size
will be obtained from the file. A discard_writes option has also been added
to provide the equivalent of a read-only file.--block-backend have been changed to more closely align
with those used by --disk.Many thanks to everyone who has contributed to our 0.7.0 release including some new faces.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Go SDK 0.6.0 — auto-generated from go-sdk-v0.6.0
Go SDK 0.6.0 — auto-generated from go-sdk-v0.6.0
CubeSandbox 0.6.0 continues to strengthen core capabilities for production deployment and operations. This release introduces 6 major features along with multiple enhancements and bug fixes. 92 commits from 31 contributors.
Deploy CubeSandbox control-plane components and compute nodes directly onto Tencent Cloud TKE, standard Kubernetes, or k3s clusters via Helm Chart. Perform rolling upgrades, canary releases, and other operations using standard Kubernetes practices. For details, see the Kubernetes Deployment Guide.
::: warning Preview Kubernetes deployment is currently in preview. Advanced capabilities such as seamless upgrades are still under active development. Feedback is welcome. :::
Introduces an E2B-compatible Volume framework that lets users plug in custom backend storage while remaining compatible with the E2B standard. Provides four hooks — Create / Destroy / Attach / Detach — and two plugin forms: Binary and RPC. This release includes Volume lifecycle management, sandbox–Volume binding APIs, and supporting SDK and cubemastercli capabilities. For details, see the Volume Plugin Guide.
Support setting an alias when creating a template, and creating sandboxes by specifying that alias.
Note: Aliases can only be set at template creation time; existing templates cannot have aliases added or changed. Specifying an alias when creating a sandbox is currently supported only in the Python SDK; other SDKs will follow soon.
Allow configuring the Host header forwarded to the sandbox (instead of the default <port>-<sandboxId>.<domain>), improving compatibility with Host-based services inside the sandbox. The new network.maskRequestHost parameter can be set when creating a sandbox to specify the Host forwarded to in-sandbox services (for example localhost:${PORT}, which expands to localhost:3000 when accessing port 3000), so applications that rely on Host for routing, validation, or callbacks work correctly.
Support isolating a compute node at the scheduling layer so operators can log in for maintenance, upgrades, and troubleshooting. After isolation, no new sandboxes are scheduled to that node; existing sandboxes continue to run unaffected.
Isolate a node with cubemastercli node isolate <node-id>, and lift isolation with the unisolate subcommand. For details, see Node Isolation.
Web console capabilities are split out of the CubeAPI module into a standalone CubeOps service, making CubeAPI lighter and more extensible.
tpl info / delete / redo.CUBE_AUTO_MIGRATION env var to skip automatic DB migration at startup for controlled upgrades.CubeSandbox 0.6.0 面向生产部署与运维持续增强关键能力。 当前版本引入了 6 个核心特性以及多个功能增强与问题修复。共计 92 个提交,来自 31 位贡献者。
支持通过 Helm Chart,将 CubeSandbox 的控制面组件和计算节点直接部署到腾讯云 TKE、标准 K8s 或 k3s 集群中。可通过标准 K8s 运维方式执行组件滚动升级、灰度发布等操作。关于 K8s 部署的详细信息请参考 K8s 部署指南。
::: warning 预览版本 K8s 部署功能当前处于预览阶段,平滑升级等高级功能仍在积极开发中,欢迎体验和反馈。 :::
新引入兼容 E2B 标准的 Volume 框架,在兼容 E2B 标准的前提下允许用户以插件形式自定义后端存储方案。提供 Create/Destroy/Attach/Detach 四个 HOOK 点,以及 Binary/RPC 两种插件形态。当前版本提供 Volume 生命周期管理、沙箱绑定 Volume 相关 API、配套 SDK 与 cubemastercli 能力。详细信息请参考 Volume 插件文档。
支持在创建模板时为模板设置别名,并通过指定别名创建沙箱。
说明:别名只能在创建模板时设置,不支持为已有模板修改别名。当前仅 Python SDK 支持指定别名创建沙箱,其他 SDK 后续即将支持。
允许配置请求转发至沙箱时的 Host(而非默认的 <port>-<sandboxId>.<domain>),更好地兼容沙箱内基于 Host 的服务。新增 network.maskRequestHost 参数,可在创建沙箱时指定转发给沙箱内服务的 Host(例如 localhost:${PORT},访问 3000 端口时展开为 localhost:3000),以便兼容依赖 Host 做路由、校验或回调的应用。
支持从调度层面“隔离”某个计算节点,便于运维时登录节点进行维护、升级和排查问题。计算节点被隔离后,将不会调度新的沙箱到该节点,存量沙箱运行不受影响。
可通过 cubemastercli node isolate <node-id> 进行节点隔离,通过 unisolate 子命令解除隔离,详细用法请参考节点相关操作。
Web 控制台相关能力从 CubeAPI 模块中剥离,独立为 CubeOps 服务,使 CubeAPI 更轻量、更具可扩展性。
tpl info / delete / redo 命令体验优化。CUBE_AUTO_MIGRATION 环境变量,可跳过启动期数据库自动迁移,便于受控升级。This release has been tracked through the 0.6.0 project.
Highlights for cloud-hypervisor version 0.6.0 include:
We continued our efforts around supporting dynamically changing the guest
resources. After adding support for CPU and memory hotplug, Cloud Hypervisor
now supports hot plugging and hot unplugging directly assigned (a.k.a. VFIO)
devices into an already running guest. This closes the features gap for
providing a complete Kata Containers workloads support with Cloud Hypervisor.
We enhanced our shared filesystem support through many virtio-fs improvements.
By adding support for DAX, parallel processing of multiple requests, FS_IO,
LSEEK and the MMIO virtio transport layer to our vhost_user_fs daemon, we
improved our filesystem sharing performance, but also made it more stable and
compatible with other virtio-fs implementations.
When choosing to offload the paravirtualized block and networking I/O to an
external process (through the vhost-user protocol), Cloud Hypervisor now
automatically spawns its default vhost-user-blk and vhost-user-net backends
into their own, separate processes.
This provides a seamless paravirtualized I/O user experience for those who want
to run their guest I/O into separate executions contexts.
More and more Cloud Hypervisor services are exposed through the
Rest API and thus only
accessible via relatively cumbersome HTTP calls. In order to abstract
those calls into a more user friendly tool, we created a Cloud Hypervisor
Command Line Interface (CLI) called ch-remote. The ch-remote binary
is created with each build and available e.g. at
cloud-hypervisor/target/debug/ch-remote when doing a debug build.
Please check ch-remote --help for a complete description of all available
commands.
In addition to the traditional Linux boot protocol, Cloud Hypervisor now supports direct kernel booting through the PVH ABI.
With the 0.6.0 release, we are welcoming a few new contributors. Many thanks to them and to everyone that contributed to this release:
chore: bump image tags from v0.6.0-rc1 to v0.6.0-rc3
chore: bump image tags from v0.6.0-rc1 to v0.6.0-rc3 (#1134)
Bump all image tag references across Makefiles, Helm chart values, docs,
and deployment scripts from v0.6.0-rc1 to v0.6.0-rc3.
## Changes
- Updated default `IMAGE_TAG` in CubeEgress, CubeProxy, and
cube-lifecycle-manager Makefiles
- Updated all image tag references in
`deploy/kubernetes/chart/values.yaml`
- Updated tag references in docs (Kubernetes guide, Terraform deploy
guide, FAQ)
- Updated deployment scripts and Terraform configs
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Signed-off-by: jinlong <jinlong@tencent.com>
fix(volume): CubeMaster/Cubelet mixed-version volumeMounts compatibil…
fix(volume): CubeMaster/Cubelet mixed-version volumeMounts compatibil…
…ity (#1123)
## Summary
- **Goal:** keep CubeMaster and Cubelet **new/old versions mutually
compatible** when sandboxes use plugin `volumeMounts` (rolling upgrades
/ mixed clusters).
- **Bug:** newer CubeMaster injected plugin volumes as
`EmptyDir(StorageMediumDefault)` placeholders plus
`plugin-volume-sources`. Older Cubelets have no plugin skip path and
treat every Default EmptyDir as a second rootfs derive
(`sb-<id>-rootfs-gen0`), which collides with `cube_rootfs_rw` and fails
create with `cubecow object already exists` (e.g. CubeAPI `130545`).
- **Fix (CubeMaster):** stop injecting Default EmptyDir for plugin
volumes; wire an empty `VolumeSource` name-only entry. New Cubelets
still Attach via the Volume Plugin framework + annotation; older
Cubelets skip the empty source in `prepareDefaultMedium` and no longer
collide on rootfs.
- **Defense (Cubelet):** keep `isPluginVolume` skip so a CubeMaster that
still sends Default EmptyDir placeholders does not break a newer
Cubelet.
### Compatibility matrix (intended)
| CubeMaster | Cubelet | Plugin volumeMounts create |
|---|---|---|
| new (this PR) | old | OK — no Default EmptyDir placeholder |
| new (this PR) | new | OK — annotation + plugin Attach |
| old (EmptyDir placeholder) | new | OK — Cubelet skips plugin EmptyDir
|
| old (no volume plugin) | old | N/A — volumes API not used |
## Test plan
- [x] Unit: `CubeMaster/pkg/service/sandbox` plugin volume annotation
test asserts no Default EmptyDir on the wire
- [x] Smoke: create sandbox with COS `volumeMounts` succeeds after
deploying fixed CubeMaster
- [x] E2E: `examples/volume/tests/e2e-volume-lifecycle.sh` with
`DRIVER=cos` and `DRIVER=cos-rpc`
- [x] SDK examples: `verify_volume.py` (cos / cos-rpc) and
`volume_complex_concurrent_test.py`
Assisted-by: Cursor:Composer
Made with [Cursor](https://cursor.com)
Signed-off-by: ls-ggg <lishuai@tencent.com>
Co-authored-by: ls-ggg <lishuai@tencent.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
v0.6.0-rc1