Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Docker application has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option

Featured Replies

I'm getting this error with Fix Common Issues plugin but I think the use case I'm using, this is expected behavior.  Wanted to throw it out there in case someone has some recommendations to alternatives or if they think it is safe to ignore.

 

I want to be able to mount my google drive as a file share to be able to use in at least one of my containers.  I found a Docker container that does just that (mitcdh/google-drive-ocamlfuse).  So what I've down is use this container to mount the google drive to a location on unRaid (I used /mnt/disks/gdrive) and then setup a volume in the other container(s) to use that location as a volume.  It seems to work great (as long as I start the containers in order).  A couple behavior things:

 

- the owner of /mnt/disks/gdrive seem to revert to root on reboot.  I'd like it to stay nobody so this all works.  Right now I'm manually fixing that on reboot.    Would a different mount location be more appropriate?

- the Fix Common Issues throws an error asking for it to be setup as slave in the container.  Doing that causes it to not work, the drive that is mounted in the google-drive container isn't visible from unraid and therefore isn't visible in the other containers.

 

Anyone have any thoughts on this?  Any bad side effects to what I'm doing?  Can I safely ignore the warning?  Is that the best location to do the mount and is there a way to keep that nobody:users ownership at the mount point?  Thanks in advance for any thoughts and suggestions.

If using slave causes problems, then ignore the error.  Nothing in FCP is definitive.

I get something similar regarding Krusader:

"Docker application binhex-krusader has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option".

 

However, my unassigned devices are accessible through Krusader.

 

I'm ignoring it then.

  • Community Expert
7 hours ago, rojarrolla said:

I get something similar regarding Krusader:

"Docker application binhex-krusader has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option".

 

However, my unassigned devices are accessible through Krusader.

 

I'm ignoring it then.

Are these all Automount?

On 4/12/2021 at 9:14 PM, trurl said:

Are these all Automount?

Yes, it is only 1 drive and it is in automount.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.