Evan Lezar

@rayburgemeestre since cri-o already supports drop-in files for overriding the config, does following a similar mechanism here work too? See https://github.com/cri-o/cri-o/blob/e0e17ee187c9f52d870b80cee9116c4fd5ca279e/pkg/config/config.go#L699 I haven't dug too much into whether only leaves...

@ArangoGutierrez this was merged as part of your e2e testing changes, correct?

@luhong123 could you please confirm your device plugin and NVIDIA Container Toolkit versions?

This is something that is under active development. We don't have a concrete release date yet, but are targetting the first quarter of 2024.

> @igorgad you do not need to manually mount `/dev/shm` in your pod spec. The device-plugin, as part of its AllocateResponse, will make sure all the entities required for MPS...

We have an issue to track making the shm size configurable. Would this be able to address your use case? What are typical values for the shared memory size?

@ettelr we have an action item to allow the size of the `/dev/shm` that is created to be specified as part of the deployment. Would this work for your use...

I have updated #666 to include a fix for this. An additional `hostDevRoot` helm value is added that can be explicitly set to `/` on systems where the root to...

Could you try to update your workload to use the following container instead: ``` nvcr.io/nvidia/k8s/cuda-sample:vectoradd-cuda11.7.1 ``` Also, is the `nvidia` runtime configured as your default runtime, or are you using...

> I found that it is possible to run the mps program directly on the host, but in the container it will prompt that `device(s) is/are busy or unavailable` Could...