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
Describe your issue
I am trying to build qiskit with rocm support and the guide makes use of Podman, when trying to run it with root permissions I get:
STEP 1/9: FROM rocm/rocm-terminal:latest
STEP 2/9: ARG UID=1000
--> Using cache 367b1e4d9e479d449789acb8d5df54f6b490ebb6e29549ce8f24b1cc671719f2
--> 367b1e4d9e4
STEP 3/9: ARG GID=1000
--> Using cache 25a10043db6e70629a9a4bc8370f51988fea052419f91409e6f7eb8f6d58f3d0
--> 25a10043db6
STEP 4/9: RUN apt update && apt install -y cmake libspdlog-dev libopenblas-dev python3-dev mpich ninja-build rocblas rocthrust && mkdir /work && chown $UID:$GID /work
error running container: from /usr/bin/crun creating container for [/bin/sh -c apt update && apt install -y cmake libspdlog-dev libopenblas-dev python3-dev mpich ninja-build rocblas rocthrust && mkdir /work && chown $UID:$GID /work]: sd-bus call: Transport endpoint is not connected: Transport endpoint is not connected
: exit status 1
ERRO[0000] did not get container create message from subprocess: EOF
Error: building at STEP "RUN apt update && apt install -y cmake libspdlog-dev libopenblas-dev python3-dev mpich ninja-build rocblas rocthrust && mkdir /work && chown $UID:$GID /work": while running runtime: exit status 1
Steps to reproduce the issue
I linked already the very small guide I was following, that is enough to reproduce and doesn't take any time at all
Issue Description
Describe your issue
I am trying to build qiskit with rocm support and the guide makes use of Podman, when trying to run it with root permissions I get:
Steps to reproduce the issue
I linked already the very small guide I was following, that is enough to reproduce and doesn't take any time at all
Describe the results you received
The container did not build
Describe the results you expected
I expected to build the container
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: