search

DataBiosphere / terra-docker

BSD 3-Clause "New" or "Revised" License
27 stars 35 forks source link

Inconsistent file permisions for /home/jupyter-user #58

Open mtmorgan opened 4 years ago

mtmorgan commented 4 years ago

It seems like all files under /home/jupyter-user should belong to jupyter-user, but some are owned by root 

[1] "total 68"                                                               
 [2] "drwxr-xr-x  1 jupyter-user users 4096 Nov 19 11:01 ."                   
 [3] "drwxr-xr-x  1 root         root  4096 Oct 24 17:28 .."                  
 [4] "-rw-r--r--  1 jupyter-user users  220 Jan  1  2000 .bash_logout"        
 [5] "-rw-r--r--  1 jupyter-user users 3836 Oct 24 17:33 .bashrc"             
 [6] "drwxr-xr-x  1 root         root  4096 Oct 24 17:32 .cache"              
 [7] "drwxr-xr-x  2 root         root  4096 Oct 24 17:33 .conda"              
 [8] "drwxrwxr-x  3 jupyter-user users 4096 Nov 19 11:01 .config"             
 [9] "drwxr-xr-x  2 root         root  4096 Oct 24 17:34 .cookiecutter_replay"
[10] "drwxr-xr-x  3 root         root  4096 Oct 24 17:34 .cookiecutters"      
[11] "drwxr-xr-x  1 jupyter-user users 4096 Oct 24 17:34 .jupyter"            
[12] "drwxr-xr-x  1 jupyter-user users 4096 Oct 24 17:34 .local"              
[13] "drwxr-xr-x 16 root         root  4096 Oct 24 17:33 miniconda"           
[14] "drwxrwxrwx  6 root         root  4096 Nov 19 11:00 notebooks"           
[15] "drwxr-xr-x  3 root         root  4096 Oct 24 17:34 .npm"                
[16] "-rw-r--r--  1 jupyter-user users  807 Jan  1  2000 .profile"            
[17] "-rw-r--r--  1 jupyter-user users   37 Oct 24 17:59 .Renviron"           
[18] "drwxr-xr-x  1 jupyter-user users 4096 Nov 19 11:12 .rpackages"

This causes problems when, for instance, an application tries to use a standard location ~/.cache/... as a file cache.

rtitle commented 4 years ago

@mtmorgan you are right, this doesn't seem ideal. We previously enforced that everything under /home/jupyter-user was owned by jupyter-user, this may have changed in the new image stack. We'll look into it..