hammerit Posted May 15, 2020 Share Posted May 15, 2020 (edited) I tried to access my drivepool drive via WSL 2 and got this. Any solution? I'm using 2.3.0.1124 BETA. ➜ fludi cd /mnt/g ➜ g ls ls: reading directory '.': Input/output error Related thread: https://community.covecube.com/index.php?/topic/5207-wsl2-support-for-drive-mounting/#comment-31212 Edited May 15, 2020 by hammerit RG9400, c_312, timmy05 and 1 other 4 Quote Link to comment Share on other sites More sharing options...
0 atomsapple Posted September 12 Share Posted September 12 On 7/11/2022 at 12:04 AM, Froghut said: I'm using a Drivepool with a bunch of Docker containers using WSL, performance is not the best but in general it works fine. Does anybody know whether any changes have been made over the last year? I'm moving to an environment where I expect to use many Docker containers to access data out of my Drivepool. I need to know whether I need to use the CIFS workaround. Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted Wednesday at 05:48 PM Share Posted Wednesday at 05:48 PM No, no changes have been made, in this regards. Quote Link to comment Share on other sites More sharing options...
Question
hammerit
I tried to access my drivepool drive via WSL 2 and got this. Any solution? I'm using 2.3.0.1124 BETA.
Related thread: https://community.covecube.com/index.php?/topic/5207-wsl2-support-for-drive-mounting/#comment-31212
Edited by hammeritLink to comment
Share on other sites
27 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.