21 minutes ago, txpenguin said:

How can I resolve this?

Switch to Advanced View using the View toggle in the top right

Brilliant - never noticed that option. Thank you - that did it.

 

How would you go about setting the slave option if you are using docker-compose through portainer?

3 minutes ago, GeoSnipes said:

How would you go about setting the slave option if you are using docker-compose through portainer?

Not to worry. Found it, just add ":rw,slave" to the end.

 

Eg:

/usr/share/elasticsearch/data:/mnt/disks/ZR12EKK3/appdata/elasticsearch/data:rw,slave

Select > Docker Section in top banner in UnRaid
Select > the docker you are having the concern with
Select > Edit (from the docker menu)

In the 'Update Container' section:
Select > Advanced View (top right of the page)
Scroll down to > Path: /data: *
Select > Edit

In the 'Edit Configuration' window:
Select > Access Mode

Select > Read/Write - Slave
Select > Save
Select > Apply

 

Once processing has finished go to Settings (in the top banner)
Select > Fix Common Problems
Select > Rescan

 

The previous error should resolve itself.

Hope that helps.
 

So what does the slave option does again? It was never answered.

 

The closest to an answer was:

On 8/11/2019 at 6:06 PM, Squid said:

Because under certain circumstancea, a container won't be able to see any files stored within a path (those mounted by the unassigned devices plugin) without the slave mode being enabled

 

I'm curious, what is enslaved? The mount on the container? The mount on the host? The [unassigned] device?

 

And also, what makes it enslaved? Why is one of the other options "Shared"—will "slave" make it …not? Is that why is it slave? As in slave to single container?