Use shiny-base:release-1.11 which reverts back to ubuntu 22 instead o… #620
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
…f 24. Also, restore libicu70 install instead of libicu74. All of this will resolve an issue installing stringi, which can be addressed with a planned upgrade in dependencies.
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.
…f 24. Also, restore libicu70 install instead of libicu74. All of this will resolve an issue installing stringi, which can be addressed with a planned upgrade in dependencies.
@lakikowolfe tagging you again to skip review. This reverts the libicu70 change earlier in the Dockerfile. It also uses a different image of shiny-base with ubuntu 22 instead of 24, which is what caused the libicu issue earlier.