We “talked” about this some times ago at:

  

      github.com/tensorflow/build
  

  
    
  
	  
  

  
    
      User in devel container
    

    
      
        opened 
        
          
        
        Jun 18, 2020
      
      


      
        
          
          bhack
        
      
    

    
    
  


  
    We still tell to users to use `HOST_PERMS` like in https://www.tensorflow.org/in…stall/source#cpu-only_2 but it is used marginally and it doesn't solve permission on your volume mount.
  

  

  
    
    
  

  


I don’t remeber if It worked in the devcontainer but generally it could be a problem without having the real user in the image/container.
If I remeber correctly I had some specific problem with the bazel cache permission with a persistent volume also on a local setup (VSCode + remote container extension).