Hi it actually is RStudio's fault ... turns out tha tin the current rocker-provided versions the `-e DISABLE_AUTH=true` bit is broken on their side ... using `-e PASSWORD=test` solves my problem ... my byzantine setup is actually fine ;) balin On 2020-09-12 20:04, Johannes Graumann wrote:
Reposted form https://community.rstudio.com/t/rstudio-server-in-docker-container-cant-acce...
Hoping for clarification(s) from the source ...
Hi,
I'm trying to get the following to run:
* In a QubesOS Xen VM running Fedora 31, I'm * using podman to run a rootless docker.io/rocker/tidyverse container as follows:
podman run -d -p 127.0.0.1:8787:8787 -v /tmp:/tmp -e ROOT=TRUE -e DISABLE_AUTH=TRUE docker.io/rocker/tidyverse
From the podman host I can test the setup using curl like so:
curl -I --user-agent 'GoogleChrome' http://localhost:8787
with the following result:
HTTP/1.1 200 OK X-Frame-Options: DENY Expires: Fri, 01 Jan 1990 00:00:00 GMT Pragma: no-cache Cache-Control: no-cache, no-store, max-age=0, must-revalidate Content-Type: text/html Content-Length: 1339 Date: Wed, 09 Sep 2020 22:38:46 GMT Connection: close X-Content-Type-Options: nosniff Server: RStudio
That looks OKish, no?
When I try however (again in the podman hosting Xen VM) to access localhost:8787 using a browser (tried firefox and chromium), the tab shows the appropriate RStudio label, yet the loading-indicating applet spins endlessly to be replaced by a message stating that R takes longer than usual to load, accompagnied by buttons for reloading, starting in safe mode and restarting the R session (none of which make any difference).
Does anyone have an inkling why I might be unable to browse to the RStudio Server installation? Is this a case of browser incompatibility fixable by using Google Chrome proper (or adjusting the user agent string (to what?))?
Thanks for any hints.
Sincerely, balin _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io