Skip to content

Add rocm-7alpha, rocm-7alpha-rocwmma and rocm-7alpha-rocwmma-improved Dockerfiles#11

Merged
kyuz0 merged 5 commits intokyuz0:mainfrom
darkbasic:rocm-7alpha
Nov 10, 2025
Merged

Add rocm-7alpha, rocm-7alpha-rocwmma and rocm-7alpha-rocwmma-improved Dockerfiles#11
kyuz0 merged 5 commits intokyuz0:mainfrom
darkbasic:rocm-7alpha

Conversation

@darkbasic
Copy link
Copy Markdown
Contributor

No description provided.

@neuhaus
Copy link
Copy Markdown
Contributor

neuhaus commented Oct 26, 2025

Thanks. I think you should call the new ones "rocm-79alpha" and "rocm-79alpha-rocwmma" otherwise it's confusing.

@darkbasic
Copy link
Copy Markdown
Contributor Author

darkbasic commented Oct 27, 2025

@neuhaus the new ones are rocm 7.10, rocm 7.9 is the existing one which is called rocm-7rc.
I didn't use 7.10 for the new one to stay consistent with the existing nomenclature that uses rc instead of the plain version number.

@darkbasic darkbasic changed the title Add rocm-7alpha and rocm-7alpha-rocwmma Dockerfiles Add rocm-7alpha, rocm-7alpha-rocwmma and rocm-7alpha-rocwmma-improved Dockerfiles Oct 29, 2025
@darkbasic
Copy link
Copy Markdown
Contributor Author

I've added a container with lhl's llama.cpp patch that doubles performance with rocwmma: ggml-org/llama.cpp#16827

@darkbasic
Copy link
Copy Markdown
Contributor Author

I've applied latest rc changes to the alpha containers and switched the improved flavor to use hjc4869's llama.cpp port.

@kyuz0 kyuz0 merged commit b213000 into kyuz0:main Nov 10, 2025
@kyuz0
Copy link
Copy Markdown
Owner

kyuz0 commented Nov 10, 2025

Thank you, sorry I missed this. I did merge it but in the weekend I am going through all the toolboxes and try to sort out the mess with the names,

I think my rocm-7rc simply tracks TheRock nightly builds @darkbasic , so it will be whatever those are building. So I think rocm-7alpha and my rocm-7rc end up being the same.

And I am happy to just keep the rocm-7alpha name or maybe even rocm-7-nightly which might be mnore accurate, and create a rocm7.1 that tracks the stable release.

@darkbasic
Copy link
Copy Markdown
Contributor Author

So I think rocm-7alpha and my rocm-7rc end up being the same.

@kyuz0 no they don't:

[niko@arch-zfs toolboxes]$ diff -ruN Dockerfile.rocm-7rc Dockerfile.rocm-7alpha
--- Dockerfile.rocm-7rc	2025-10-15 08:34:55.141521766 +0200
+++ Dockerfile.rocm-7alpha	2025-11-09 15:57:19.237391720 +0100
@@ -6,7 +6,7 @@
        radeontop git vim patch curl ninja-build tar xz aria2c \
     && dnf clean all && rm -rf /var/cache/dnf/*
 
-# find & fetch the latest Linux 7.x.x rc tarball (gfx1151)
+# find & fetch the latest Linux 7.x.x tarball (gfx1151)
 WORKDIR /tmp
 ARG ROCM_MAJOR_VER=7
 ARG GFX=gfx1151
@@ -14,8 +14,9 @@
     BASE="https://therock-nightly-tarball.s3.amazonaws.com"; \
     PREFIX="therock-dist-linux-${GFX}-${ROCM_MAJOR_VER}"; \
     KEY="$(curl -s "${BASE}?list-type=2&prefix=${PREFIX}" \
-      | grep -o "therock-dist-linux-${GFX}-${ROCM_MAJOR_VER}\.[0-9]\+\.[0-9]\+rc[0-9]\{8\}\.tar\.gz" \
-      | sort | tail -n1)"; \
+      | tr '<' '\n' \
+      | grep -o "therock-dist-linux-${GFX}-${ROCM_MAJOR_VER}\..*\.tar\.gz" \
+      | sort -V | tail -n1)"; \
     echo "Latest tarball: ${KEY}"; \
     aria2c -x 16 -s 16 -j 16 --file-allocation=none "${BASE}/${KEY}" -o therock.tar.gz
 RUN mkdir -p /opt/rocm-7.0 \

rocm-7rc tracks the "rc" nightlies while rocm-7alpha tracks the latest "alpha" nightly.

This is what each of them would download right now:

image

By the way I've just realized that I forgot to update refresh-toolboxes.sh so I'll open another PR for that.

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