You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For installing PyTorch, you can start from a fresh docker image, e.g, `rocm/pytorch:rocm6.2_ubuntu20.04_py3.9_pytorch_release_2.3.0`, `rocm/pytorch-nightly`.
27
+
For installing PyTorch, you can start from a fresh docker image, e.g, `rocm/pytorch:rocm6.3_ubuntu24.04_py3.12_pytorch_release_2.4.0`, `rocm/pytorch-nightly`. If you are using docker image, you can skip to Step 3.
28
28
29
-
Alternatively, you can install PyTorch using PyTorch wheels. You can check PyTorch installation guide in PyTorch [Getting Started](https://pytorch.org/get-started/locally/)
29
+
Alternatively, you can install PyTorch using PyTorch wheels. You can check PyTorch installation guide in PyTorch [Getting Started](https://pytorch.org/get-started/locally/). Example:
1. Install [Triton flash attention for ROCm](https://github.com/ROCm/triton)
32
38
@@ -37,7 +43,7 @@ Currently, there are no pre-built ROCm wheels.
37
43
pip uninstall -y triton
38
44
git clone https://github.com/OpenAI/triton.git
39
45
cd triton
40
-
git checkout e192dba
46
+
git checkout e5be006
41
47
cd python
42
48
pip3 install .
43
49
cd ../..
@@ -49,15 +55,15 @@ Currently, there are no pre-built ROCm wheels.
49
55
50
56
2. Optionally, if you choose to use CK flash attention, you can install [flash attention for ROCm](https://github.com/ROCm/flash-attention/tree/ck_tile)
51
57
52
-
Install ROCm's flash attention (v2.5.9.post1) following the instructions from [ROCm/flash-attention](https://github.com/ROCm/flash-attention/tree/ck_tile#amd-gpurocm-support)
58
+
Install ROCm's flash attention (v2.7.2) following the instructions from [ROCm/flash-attention](https://github.com/ROCm/flash-attention/tree/ck_tile#amd-gpurocm-support)
53
59
Alternatively, wheels intended for vLLM use can be accessed under the releases.
54
60
55
-
For example, for ROCm 6.2, suppose your gfx arch is `gfx90a`. To get your gfx architecture, run `rocminfo |grep gfx`.
61
+
For example, for ROCm 6.3, suppose your gfx arch is `gfx90a`. To get your gfx architecture, run `rocminfo |grep gfx`.
@@ -104,7 +106,7 @@ Currently, there are no pre-built ROCm wheels.
104
106
For vLLM, please refer to [vLLM performance optimization](https://rocm.docs.amd.com/en/latest/how-to/tuning-guides/mi300x/workload.html#vllm-performance-optimization).
105
107
:::
106
108
107
-
## Set up using Docker
109
+
## Set up using Docker (Recommended)
108
110
109
111
### Pre-built images
110
112
@@ -120,7 +122,12 @@ for instructions on how to use this prebuilt docker image.
120
122
121
123
Building the Docker image from source is the recommended way to use vLLM with ROCm.
122
124
123
-
First, build a docker image from <gh-file:Dockerfile.rocm> and launch a docker container from the image.
125
+
#### (Optional) Build an image with ROCm software stack
126
+
127
+
Build a docker image from <gh-file:Dockerfile.rocm_base> which setup ROCm software stack needed by the vLLM.
128
+
**This step is optional as this rocm_base image is usually prebuilt and store at [Docker Hub](https://hub.docker.com/r/rocm/vllm-dev) under tag `rocm/vllm-dev:base` to speed up user experience.**
129
+
If you choose to build this rocm_base image yourself, the steps are as follows.
130
+
124
131
It is important that the user kicks off the docker build using buildkit. Either the user put DOCKER_BUILDKIT=1 as environment variable when calling docker build command, or the user needs to setup buildkit in the docker daemon configuration /etc/docker/daemon.json as follows and restart the daemon:
125
132
126
133
```console
@@ -131,7 +138,26 @@ It is important that the user kicks off the docker build using buildkit. Either
131
138
}
132
139
```
133
140
134
-
<gh-file:Dockerfile.rocm> uses ROCm 6.2 by default, but also supports ROCm 5.7, 6.0 and 6.1 in older vLLM branches.
141
+
To build vllm on ROCm 6.3 for MI200 and MI300 series, you can use the default:
First, build a docker image from <gh-file:Dockerfile.rocm> and launch a docker container from the image.
150
+
It is important that the user kicks off the docker build using buildkit. Either the user put `DOCKER_BUILDKIT=1` as environment variable when calling docker build command, or the user needs to setup buildkit in the docker daemon configuration /etc/docker/daemon.json as follows and restart the daemon:
151
+
152
+
```console
153
+
{
154
+
"features": {
155
+
"buildkit": true
156
+
}
157
+
}
158
+
```
159
+
160
+
<gh-file:Dockerfile.rocm> uses ROCm 6.3 by default, but also supports ROCm 5.7, 6.0, 6.1, and 6.2, in older vLLM branches.
135
161
It provides flexibility to customize the build of docker image using the following arguments:
136
162
137
163
-`BASE_IMAGE`: specifies the base image used when running `docker build`. The default value `rocm/vllm-dev:base` is an image published and maintained by AMD. It is being built using <gh-file:Dockerfile.rocm_base>
@@ -141,13 +167,13 @@ It provides flexibility to customize the build of docker image using the followi
141
167
142
168
Their values can be passed in when running `docker build` with `--build-arg` options.
143
169
144
-
To build vllm on ROCm 6.2 for MI200 and MI300 series, you can use the default:
170
+
To build vllm on ROCm 6.3 for MI200 and MI300 series, you can use the default:
0 commit comments