mlcommons / mlcommons/mlcube

Running MLBoxes on windows machines.

Open
#136 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
160
Forks
31
PR merge metrics
No merged PRs in 30d

Description

Docker and other MLCommons-Box runners assume they run in Linux environment. Several updates are required to support windows machines as well. Let's use this thread to track what is required and also document the process of running boxes on windows.

__How to run docker-based MLBoxes on Windows machines?

  • Do this ...
  • Do that ...

Fixed:

  • docker run command #134.

To be fixed:

  • docker inspect command that uses /dev/null. Error:
    Could not find a part of the path 'C:\dev\null'
    
    Seems like it should either be removed for windows platform (that /dev/null), or the docker runner needs to be able to figure out where it runs (cmd, power shell). Depending on environment, either NUL or $null are used.
  • The function that creates mount points needs to be updated. Currently, for file names the following is generated:
    mounts:
        C:\mlperf\mlbox_11062020\box_examples\mnist\workspace/parameters: '/mlbox_io1/C:\mlperf\mlbox_11062020\box_examples\mnist\workspace/parameters'
    
  • Paths on a command line need to be quoted.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Docker runner code that handles docker inspect, mount-point creation, and command-line paths, then reproduce the listed failures on a Windows machine. Check how /dev/null, Windows path separators, and quoting are currently handled. Done means Docker-based MLBoxes run on Windows without these errors and the Windows setup process is documented in this issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
cli, devops, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.