Skip to content

[Feature]: Make ROCm Docker UX Intuitive - Achieve User Experience Parity with NVIDIA #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
OrenLeung opened this issue Mar 8, 2025 · 0 comments

Comments

@OrenLeung
Copy link

Suggestion Description

There is lots of room for improvement on ROCm docker UX. On NVIDIA GPUs, end users just do --gpus all but on AMD, i need to type like 8 additional different flags.

i know this issue seems minor but it is tons of minors quirks across the ROCm ecosystem that hurts the user experience.

any chance, AMD could work with docker corp to make AMD GPUs also just be also as simple as --gpus all?

Currently

on NVIDIA GPUs, users just need to add 1 flag

docker run --gpu alls ...

Currently on ROCm GPUs, user need to a bunch of flags

sudo docker run --network=host \
    --device=/dev/kfd \
    --device=/dev/dri \
    --ipc=host \
    --shm-size 16G \
    --group-add video \
    --cap-add=SYS_PTRACE \
    --security-opt seccomp=unconfined
   ...

Suggestion

ROCm follows the UX pattern on NVIDIA GPUs and users just need to add 1 flag

docker run --gpu alls ...

cc: @hliuca and @powderluv

Operating System

No response

GPU

No response

ROCm Component

No response

@OrenLeung OrenLeung changed the title [Feature]: Make ROCm Docker UX Intuitive [Feature]: Make ROCm Docker UX Intuitive - Achieve Parity with NVIDIA Mar 8, 2025
@OrenLeung OrenLeung changed the title [Feature]: Make ROCm Docker UX Intuitive - Achieve Parity with NVIDIA [Feature]: Make ROCm Docker UX Intuitive - Achieve User Experience Parity with NVIDIA Mar 8, 2025
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

No branches or pull requests

1 participant