This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
Fixed issue in which datalab does not start for GPU instances #2147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… it fails to pull down the docker container - Updated the NVIDA driver to 418.67 - Added ExecStop and ExecStopPost to the datalab service so systemctl can be used to stop the service.
|
@emailbob When will this issue fix merge? |
|
Can we get this done, PLEASE!? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed issue for the GPU instance in which it does not start because it fails to pull down the docker container (Google Cloud Datalab Connect Failing with Beta Gpu Instance #2133)
Updated the NVIDA driver to 418.67
Added ExecStop and ExecStopPost to the datalab service so systemctl can be used to stop the service.