Skip to content

Add dockerfile for building TheRock#4744

Open
causten wants to merge 7 commits intodevelopfrom
buildtherock
Open

Add dockerfile for building TheRock#4744
causten wants to merge 7 commits intodevelopfrom
buildtherock

Conversation

@causten
Copy link
Copy Markdown
Collaborator

@causten causten commented Apr 6, 2026

Motivation

Add support for building when TheRock was installed via PIP

Technical Details

Created a docker that installs TheRock via pip, added build instructions via a .md file

Changelog Category

Add a CHANGELOG.md entry for any option other than Not Applicable

    • Added: New functionality.
    • Changed: Changes to existing functionality.
    • Removed: Functionality or support that has been removed. (Compared to a previous release)
    • Optimized: Component performance that has been optimized or improved.
    • Resolved Issues: Known issues from a previous version that have been resolved.
    • Not Applicable: This PR is not to be included in the changelog.

@causten causten requested a review from a team as a code owner April 6, 2026 17:41
@causten causten requested review from Copilot and kentqian April 6, 2026 17:41
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a Docker-based workflow to build MIGraphX in a TheRock-style ROCm environment installed via pip, and documents how to use it.

Changes:

  • Added a new Dockerfile that creates a ROCm SDK Python venv and wires /opt/rocm to the TheRock SDK layout.
  • Added a new install/build guide describing how to build MIGraphX using the therock package backend inside that container.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
tools/docker/dockerfile.therock New Ubuntu 24.04 image that installs ROCm SDK (nightlies) via pip into a venv and installs rbuild.
docs/install/build-migraphx-therock.md New guide documenting building MIGraphX using the TheRock environment and MIGRAPHX_PACKAGE_BACKEND=therock.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +34 to +43
Launch an interactive container with GPU device access and a workspace mount (adjust paths and image name to match your setup):

```bash
docker run -it --network=host --device=/dev/kfd --device=/dev/dri --group-add video \
-v $HOME/code:/workspace \
migraphx-therock:latest
```

Inside the container, work from your MIGraphX source tree (for example under `/workspace/AMDMIGraphX` if you cloned into `$HOME/code` on the host).

Copy link

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The container example mounts the repo under /workspace, but the Dockerfile sets WORKDIR /work, and later text assumes the source tree is under /workspace/.... Consider aligning the Dockerfile WORKDIR and the documented mount point (or update the example) to avoid confusing users.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants