Add chromium-swiftshader to enable webGL #338
Open
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
adkinsjd
force-pushed
the
adkins/add-chromium-swiftshader
branch
from
10d4261
to
ad74448
Compare
|
|
|
👍 |
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.
Image rendering of panels depending on webGL (such as mapbox plots in the plotly plugin https://grafana.com/grafana/plugins/ae3e-plotly-panel/) does not work with this container. The renderer tries but fails to initialize webGL.
Adding chromium-swiftshader along with the "--use-gl=swiftshader" command line argument solves the issue.
This PR adds chromium-swiftshader to the apk package list. The command line argument can be added through the current config mechanism.