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
CDI spec devices are not valid input in all device input locations #16232
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
A friendly reminder that this issue had no activity for 30 days. |
@giuseppe PTAL |
first half of the fix: containers/common#1239 |
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Nov 21, 2022
Closes: containers#16232 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
and second half: #16580 |
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Nov 24, 2022
Closes: containers#16232 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Nov 25, 2022
Closes: containers#16232 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 9, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
Although it is now possible to list a CDI spec during
podman run
, there are a few other places where devices can be specified where the CDI spec appears to not be allowed.Steps to reproduce the issue:
Install podman and the nvidia-container-toolkit, and generate the relevant CDI spec.
Modify the containers config:
sudo sed -i 's|^#devices = \[\]|devices = ["nvidia.com/gpu=gpu0"]|;' /usr/share/containers/containers.conf
Run a gpu-enabled container:
podman run --rm docker.io/nvidia/cudagl:11.4.2-runtime-ubuntu20.04 nvidia-smi
Describe the results you received:
Describe the results you expected:
The container runs successfully, and produces output from
nvidia-smi
Additional information you deem important (e.g. issue happens only occasionally):
I'm also attempting to use devices in a gitlab-runner via the podman socket, and something in the chain seems to be trying to
stat
the device line. That is, I get this error during a run:ERROR: Job failed (system failure): prepare environment: Error response from daemon: container create: stat nvidia.com/gpu=gpu0: no such file or directory (docker.go:659:0s). Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information
... this is somewhat more unsupported, however...
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes - package is from Kubic repo
Additional environment details (AWS, VirtualBox, physical, etc.):
Host OS: Ubuntu 22.04
The text was updated successfully, but these errors were encountered: