-
Notifications
You must be signed in to change notification settings - Fork 401
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
Add info on docker usage to rocm install instructions #1242
Conversation
See comments here for more information https://gist.github.com/guilt/6c901f7ac0a726685b6334798da77c00?permalink_comment_id=5131866#gistcomment-5131866
The terminology for "docker.io" (as opposed to Docker Desktop) is Docker Engine or Docker CE: https://docs.docker.com/engine/install/ I think it'd make sense to provide a link to Docker's installation instructions as an alternative to the Ubuntu-packaged version, since Docker recommends using their own repo: https://docs.docker.com/engine/install/ubuntu/ Aside from that, this looks reasonable. It's expected that Docker commands require sudo; other options such as Podman would allow rootless containers. |
Makes sense. I haven't tried Docker CE, but I assumed docker io was recommended as it's in the CUDA instructions: https://support.system76.com/articles/cuda |
You are using the Ubuntu package for Docker CE. |
@jacobgkau I edited the PR per your comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! The linked AMD tutorial works on pang12.
@jacobgkau the current ROCm install instructions are for ROCm version 6.1. I'm curious if you have been able to install version 6.2? In theory we should just be able to edit the file Let me know if there's a better place to ask for help on this. $ sudo apt install rocm --upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
rocm : Depends: rocm-utils (= 6.2.0.60200-66~22.04) but 6.2.1.60201-112~22.04 is to be installed
Depends: rocm-developer-tools (= 6.2.0.60200-66~22.04) but 6.2.1.60201-112~22.04 is to be installed
Depends: rocm-openmp-sdk (= 6.2.0.60200-66~22.04) but 6.2.1.60201-112~22.04 is to be installed
Depends: rocm-opencl-sdk (= 6.2.0.60200-66~22.04) but 6.2.1.60201-112~22.04 is to be installed
Depends: rocm-ml-sdk (= 6.2.0.60200-66~22.04) but 6.2.1.60201-112~22.04 is to be installed
Depends: mivisionx (= 3.0.0.60200-66~22.04) but 2.5.0.60100-82~22.04 is to be installed
Depends: migraphx (= 2.10.0.60200-66~22.04) but 2.10.0.60201-112~22.04 is to be installed
Depends: rpp (= 1.8.0.60200-66~22.04) but 1.8.0.60201-112~22.04 is to be installed
Depends: rocm-core (= 6.2.0.60200-66~22.04) but 6.2.1.60201-112~22.04 is to be installed
Depends: migraphx-dev (= 2.10.0.60200-66~22.04) but 2.10.0.60201-112~22.04 is to be installed
Depends: mivisionx-dev (= 3.0.0.60200-66~22.04) but it is not going to be installed
E: Unable to correct problems, you have held broken packages. |
@jessecambon Why did you specify I'm getting a different error from you when trying to install version 6.2.0 with
I get the same message with |
@jacobgkau |
I ran into some permissions issues using Docker Desktop with ROCM and was able to resolve these issues by using docker.io instead and running docker as sudo. You can refer to the comments here for more information.
I thought it would be good to add a note here so that others can avoid these issues.