Supporting R on top of databricks standard ubuntu 18 image with few R… #59
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
… fixes and supports DBR 8.x
|
@rohan-viz sorry for this late comment. Do you mind updating this to ubuntu 20.04? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
R fixes mentioned in #54 and supports DBR 8.x
A very common use case for people using databricks is that they want to add libraries and any custom installations at image creation time only so that the cluster start times are reduced. For this they want to start with a base image which contains most of the standard Databricks Runtime stuff.
Similar was a use case with me but when I tried to get the standard image, it lacked R. And then there were some issues based on DBR 8.X when I tried composing from the existing image.
Fixes:
Using the correct cran repo
Using DEBIAN_FRONTEND="noninteractive" mode
Interpreter REPL not starting issue was fixed by “shiny” package installation
Committing the image hoping it will be useful for others in the same journey.