So we recently followed the instructions in this thread to deploy RStudio on OOD without singularity. We did this for a couple reasons. The 1st was that we want to upgrade to newer versions of RStudio and the 2nd was that the singularity container was preventing certain popular tools (future.batchtools) from seeing our clusters scheduler (which was more a limitation caused by the PBS scheduler than the container, but this was one way to solve it).
The only problem is that we turn on authentication with --auth-none, it give us this:
We are VERY mystified about that username. It feels like it should be a major clue, but we don’t know where that is coming from.
And we are also confused as to why this does not log us in as it used to before we switched away from the almost empty singularity container. Pasting in the expected username and the generated password while it’s running also does not work. And from other testing, it seems that the --auth-pam-helper-path argument is really not respecting the values for the username and password that are generated and reported by the script.sh.erb
Anyone have an idea about what’s happening? The script inside of template/bin/auth certainly seems simple enough. But I wish I could get a bit more insight into what it sees when it is running.