microsoft / microsoft/OmniParser
omnitool on arm64
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 25.4k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
I am getting this warning when I am trying to setup omnitool.
I am setting up omnitool in a debian-based vm in UTM, which supports nested virt on apple silicon
docker logs omni-windows
❯ Starting Windows for Docker v0.00...
❯ For support visit https://github.com/dockur/windows-arm
❯ CPU: 0 | RAM: 9/12 GB | DISK: 491 GB (btrfs) | KERNEL: 6.11.2-arm64...
❯ Extracting local ISO image...
❯ Detecting version from ISO image...
❯ Detected: Windows 11 Enterprise (Evaluation)
❯ Warning: the answer file for Windows 11 Enterprise (Evaluation) was not found (win11arm64-enterprise-eval.xml).
❯ Adding drivers to image...
❯ Adding OEM folder to image...
❯ Adding win11arm64.xml for automatic installation...
❯ Building Windows 11 image...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the setup in a Debian-based ARM64 VM under UTM and inspect docker logs omni-windows, the entry point shown in the report. Determine whether the missing win11arm64-enterprise-eval.xml prevents setup, then verify the warning's behavior during the ARM64 installation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, docker
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100