Skip to content
This repository has been archived by the owner on Oct 27, 2023. It is now read-only.

Fix bug causing GPU unavaliable after updating container resource #55

Closed
wants to merge 1 commit into from
Closed

Conversation

tkanng
Copy link

@tkanng tkanng commented May 1, 2019

No description provided.

@tkanng tkanng closed this May 3, 2019
@tkanng tkanng changed the title Fix bug causing GPU unavaliable after updating container resource Fix bug May 3, 2019
@Davidrjx
Copy link

@tkanng hi, why closing the pr? i also ran into the same problem.

@tkanng
Copy link
Author

tkanng commented May 20, 2019

Hi, @Davidrjx The PR can fix the problem, just merge it ! I close the PR, because it seems there's no plan to merge it. :) If you want to know the reason causing the problem and how to fix it , feel free to contact with me!

@dragonofac
Copy link

dragonofac commented Jul 16, 2019

@tkanng
So, what cause the nvml unknown error in the container when '--cpu-manager-policy=static' option is open ?
And how could I fixed it if the patch not merged?

@tkanng
Copy link
Author

tkanng commented Oct 2, 2019 via email

@Davidrjx
Copy link

@tkanng thanks

@tkanng tkanng changed the title Fix bug Fix bug causing GPU unavaliable after updating container resource Mar 7, 2020
@Davidrjx
Copy link

@ruster-cn @tkanng's PR should be right, my local test currently is ok. Just add above similar logic into newer Docker runtime, like v19.03.*, then have related nvidia-runtime updated along with docker. At this time, dockerd and nvidia-container should reference same runtime.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants