October 10, 20169 yr This may be a defect. Description: When you add a drive to the array, it gets formatted. When you start a Dockerized app such as Krusader and view the contents of the new disk on /mnt/diskX, it does not see any files. If you stop and restart the docker service and the app, the app can see the contents of the drive. How to reproduce: Start the unRAID server with a new drive. Add the drive to the array, start the array, and format the drive. Wait for the formatting to complete. From another PC, create a directory on the newly added drive through the DiskX share that's exported. Open a Dockerized app such as Krusader. Expected results: Krusader should see the directory added. Actual results: Krusader does not see the newly added directory. Other information: Stop the Dockerized app and restart the Docker service and start the Dockerized app. It can now see the newly added directory. This happens verify infrequently since adding a new drive is a rare occurrence. It also has an easy work around. A reminder to restart the docker service would be nice.
October 10, 20169 yr Well known that docker can't see drives that are mounted after the service starts. Also, unless a bug can be reproduced on the current stable version there's not too much point reporting as I don't think fixes are going to get backported to old Unraid versions.
Archived
This topic is now archived and is closed to further replies.