RStudio docker image: startup.sh error message: -e not found

Question

RStudio docker image: startup.sh error message: -e not found

Closed this issue 4 years ago · 11 comments

I have just built the image for RStudio from

https://github.com/ppc64le/build-scripts/blob/master/rstudio/Dockerfiles/v1.2.1335/Dockerfile

and tried to start a container with

sudo docker run -i -p 8787:8787 rstudio

but I cannot connect to RStudio Server via the browser with localhost:8787
because the docker container shows this error message:

/startup.sh: 1: /startup.sh: -e: not found

The reason seems to be that the first line of the script contains an "-e".

This may possibly be caused by this line in the run part of the Dockerfile

echo -e '#!/bin/bash\ncd /usr/sbin\nrstudio-server start' >> startup.sh && \

Answer 1 · 2020-01-31T14:34:57.000Z

I forgot to mention that I am using Fedora release 31 (Thirty One) on an IBM Power9 8-core CPU (revision 2.3 pvr 004e 1203) with kernel version 5.4.13-201.fc31.ppc64le and Xfce as Desktop.

docker version says:

Client:
Version: 18.09.8
API version: 1.39
Go version: go1.13beta1
OS/Arch: linux/ppc64le
Experimental: false

Server:
Engine:
Version: 18.09.8
API version: 1.39 (minimum version 1.12)
etc. (same as client)

Answer 2 · 2020-02-18T06:53:39.000Z

@sarveshtamba is working on this

Answer 3 · 2020-02-18T08:41:35.000Z

Fixed and tested. Raised PR at #137

Answer 4 · 2020-02-19T05:35:45.000Z

@aryoda can you please try to build RStudio docker image from the updated Dockerfile now and let us know the result at your end?

Answer 5 · 2020-02-19T07:02:31.000Z

@sarveshtamba Thanks for fixing the issue. I am really sorry but I cannot test the fix currently since my power9 hardware has a defect and a replacement will take about two months due to the required RMA procedure and the complicated customs clearance (I am privately sponsoring the power9 support of R so I cannot just buy another machine).

I will try to find somebody else via a forum post...

Answer 6 · 2020-02-19T10:33:06.000Z

@aryoda sure, do let us know in case you need any further assistance.

Answer 7 · 2020-02-19T19:33:52.000Z

@aryoda is there any chance that you can test on the systems at Oregon State University's Open Source Lab: https://osuosl.org/services/powerdev/ to do a build/test in the interim?

Answer 8 · 2020-04-02T05:43:22.000Z

@aryoda - any comments on above ?

Answer 9 · 2020-04-02T07:57:22.000Z

Oh, forgive me my late feed-back. What a pity nobody followed my request for testing in the forum I have asked for help :-(

I personally wanted to test the fix on exactly the same hardware/OS/app layer constellation
but I am still in the RMA phase of my hardware and delivery bottle-necks do affect my new hardware (current estimation is 4 - 6 more weeks until I can get my replacement hardware).

Thanks for the link to the Oregon State University Open Source Lab initiative. I think testing there would not add value to the tests you have already done so I prefer to wait for my hardware (where the already installed software stack is waiting on the SSD to be reapplied).

So I propose to publish the fix ASAP for now.

I will come back for a retest as soon as I get my new hardware - promised :-)

Answer 10 · 2020-04-02T11:01:45.000Z

And: I can close this issue if you want - I will retest it anyhow

Answer 11 · 2020-04-08T07:31:43.000Z

Thanks @aryoda for reporting and following up on this, since we were able to replicate, fix and test the issue on our side, I am closing this for now, Please feel free to re-open or create another issue if you still find problems in your testing, thank you!