-
Notifications
You must be signed in to change notification settings - Fork 3k
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
libXrender.so.1 is required to display R plots inline #54
Comments
Need to resolve rebuild problem in #55 first. Then can fix this. |
Sounds good. |
It's actually installed in r-notebook (https://github.com/jupyter/docker-stacks/blob/master/r-notebook/Dockerfile#L13) and datascience-notebook. I'm guessing you're using all-spark-notebook where it's not. |
Right, I should have said it was for all-spark-notebook. |
Merged and rebuilt. If you hit any other problems on the latest build, give a shout. |
Just tested and it works fine. Thanks for the quick build. |
I have the same error in a Linux AMI from Amazon in AWS. |
@diegocgaona which stack image are you using? |
@parente Amazon Linux AMI 2015.09.1 (HVM), SSD Volume Type - ami-60b6c60a |
I'm sorry, I meant which of the Docker container images in this repository are you using? If you're not using one of them, and are installing directly to the VM, then you need to replicate the Docker image contents, in particular the libxrender1 package installed here: https://github.com/jupyter/docker-stacks/blob/master/minimal-notebook/Dockerfile#L28 |
Adding auth0 OAuthenticator implementation
R plots such as the following only create a RPlots.pdf file in the working directory, then issue an error:
x<-1:10 plot(x)
output is:
Error in file(con, "rb"): cannot open the connection
Error in file(con, "rb"): cannot open the connection
Error in file(con, "rb"): cannot open the connection
Error in file(con, "rb"): cannot open the connection
plot without title
Installing the lib in the container with the following fixes the error
sudo apt-get install libxrender1
This issue is linked to #51
The text was updated successfully, but these errors were encountered: