Closed hongooi73 closed 2 years ago
Good question. I only ever played a little with sshfs on my local machines here, and very rarely with remote ones I had ssh access for.
The base image of rocker/rstudio:latest
is now rocker/r-ver:4.1.2
, and the base image of rocker/r-ver:4.1.2
is ubuntu:focal
(same with jupyter/datascience-notebook
).
Is it work fine on rocker/r-ver:4.1.2
?
If I search for the error I can find the answer that we need the --privileged
option of the docker run
command.
https://github.com/s3fs-fuse/s3fs-fuse/issues/647
@eitsupi adding --privileged
did the trick. Thanks so much!
Bit weird that Ubuntu doesn't need this flag, but oh well, as long as it works.
--privileged
is generally considered to be undesirable for security reasons, I believe.
If it works for the root user on ubuntu:focal
, I have no idea why it would not work for the root user on rocker/rstudio
.
What was the user when you ran the command in each container?
The default user of jupyter/datascience-notebook
is jovyan, did you run the command as jovyan?
Hi Dirk/Carl,
I'm trying to use sshfs to connect to the filesystem on one of our servers. Everything works when I do this inside an Ubuntu-based container (jupyter/datascience-notebook to be precise) but I get the above error when I try it with rocker/rstudio.
Things are complicated slightly by the fact that I also have to set some proxy info/copy certs into the image for it to connect to our network. Here is a minimal example of the dockerfile I use to do this:
In the image, I then run
But this results in the error shown above. The same code works without issue in an Ubuntu container, as noted.
Is there some trick to getting sshfs to work on rocker and/or Debian?