Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker issues #54

Closed
bschilder opened this issue Jan 4, 2022 · 2 comments
Closed

Docker issues #54

bschilder opened this issue Jan 4, 2022 · 2 comments
Labels

Comments

@bschilder
Copy link
Collaborator

Docker container of EWCE works fine until you try to print some plots.

Just noticed this warning message:

R graphics engine version 15 is not supported by this version of RStudio. The Plots tab will be disabled until a newer version of RStudio is installed. 

Apparently this happens when the version of R is too far ahead of the version of Rstudio. For some reason there is no back compatibility?
https://community.rstudio.com/t/warning-message-r-graphics-engine-version-14-is-not-supported-by-this-version-of-rstudio-the-plots-tab-will-be-disabled-until-a-newer-version-of-rstudio-is-installed/110386

Source

Our Dockerfile currently uses bioconductor/bioconductor_docker:devel as the base. Which means that this is an issue with how Bioconductor is setting up their docker container, not ours.

Potential solutions

We could try changing our Dockerfile to one of the following:

  • bioconductor/bioconductor_docker:latest: May not always be accurate. Maintainer doesn't seem keen on keep this up to date, though a verdict on this was never communicated.
  • bioconductor/bioconductor_docker:RELEASE_3_14: Should work, but means we will have to remember to manually update the Dockerfile anytime there is a new release. My intent with using thelatest tag was to avoid this and make the file usable in the long-term as is.

Or we could simply wait until the bioconductor_docker maintainer fixes the issue, and then rebuild any containers that used that version. I've posted the Issue here:
Bioconductor/bioconductor_docker#39

@Al-Murphy
Copy link
Collaborator

Based on what you have here, makes most sense to me to wait to see if a fix is put in by the bioconductor_docker maintainer. The way you currently have the automated docker builds set up is the most logical.

@bschilder bschilder added the bug label Mar 8, 2022
@bschilder
Copy link
Collaborator Author

This has since been resolved after the bioconductor_docker update.

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

No branches or pull requests

2 participants