to_disk on Windows

未关闭
#165 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
rust
领域
backend

调研方向

Start by reading the existing Linux to_disk implementation on the main branch and its xattr-based cache handling. The issue proposes Windows caching, raw-to-VHDX conversion, and a Podman machine workflow, but does not name files or tests. Done would mean implementing and validating that Windows workflow; its design decisions are still open.

由索引模型根据 Issue 内容生成。

描述

One of the first commands to implement on Windows is to_disk.
We should have a similar workflow as done on linux. This is my idea of it

  • Phase 0: Check for existing cached disk image
    The current code uses extended attributes (xattrs) for handling the cache. On Windows this does not work as rustix cannot be imported. However, NTFS supports a kind of extended attributes (NTFS Alternate Data Stream) so we could try to use a library which is cross-platform (suggestions??), otherwise we should have a mechanism to store data in a sidecar metadata file or leverage the Registry.

  • Phase 1: Validation and preparation
    This should work similarly to what we have on the main branch. NTFS supports sparse file so we could reuse the current code. The difference is that we need to create a temporary image. We first create a raw image and then convert it to a vhd/vhdx image.

  • Phase 3 -5
    We create a new podman machine using hyper-v (which shares a volume where the final .vhdx image will be stored) and execute the code/scripts used for linux (maybe instead of using the source image as the installer environment we should use a custom image?), then we leverage qemu-img to convert the resulting .raw to .vhdx. The podman machine is deleted (or should we keep it there for bootc purposes and just stop it?) and the host is able to use the .vhdx for further operations.

主要语言
Rust
星标
142
派生
40
平均合并
2 天 22 小时
30 天内合并 PR
10

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bootc-dev/bcvk 的其他 Issue

查看 bootc-dev/bcvk 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。