Leaderboard

I have a Bluetooth dongle that I want to use in a docker container. Docker requires that the Host OS install drivers for the device before it can be passed to the container. Searching the forums it appears I am not alone in that need, particularly for the users of Home Assistant. See this post for more info:

Application Name: Nextcloud Application Site: https://nextcloud.com/ Docker Hub: https://hub.docker.com/r/linuxserver/nextcloud/ Github: https://github.com/linuxserver/docker-nextcloud Note: Requires MariaDB or MySQL, please note the issues with binlogging detailed here. This is a Nextcloud issue which we have no control over. https://info.linuxserver.io/issues/2023-06-25-nextcloud/ For setup guide please see the article on our website here. Image is now upgrading Nextcloud internally For upgrading the Nextcloud version there are 3 options. 1. Update via the webui when the upgrade shows as available. 2. Update from the terminal when the upgrade shows as available with: docker exec -it nextcloud updater.phar 3. Manual upgrade using occ. ##Turn on maintenance mode docker exec -it nextcloud occ maintenance:mode --on ##Backup current nextcloud install docker exec -it nextcloud mv /config/www/nextcloud /config/www/nextcloud-backup ##Grab newest nextcloud release and unpack it docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest.tar.bz2 -P /config docker exec -it nextcloud tar -xvf /config/latest.tar.bz2 -C /config/www ##Copy across old config.php from backup docker exec -it nextcloud cp /config/www/nextcloud-backup/config/config.php /config/www/nextcloud/config/config.php ##Now Restart docker container docker restart nextcloud ##Perform upgrade docker exec -it nextcloud occ upgrade ##Turn off maintenance mode docker exec -it nextcloud occ maintenance:mode --off ## Now Restart docker container docker restart nextcloud Once all is confirmed as working: ##Remove backup folder docker exec -it nextcloud rm -rf /config/www/nextcloud-backup ##Remove Nextcloud tar file docker exec -it nextcloud rm /config/latest.tar.bz2 Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

So you have port 81 (external internet facing) port forwarded to port 81 on your unraid and inside the container is port 80, is that correct? saarg beat me to it.

Of course it's possible to add more fine grained shares/paths, but since I'm the only user with access to this server, I don't bother.

No, I added a new path config to the docker template, with the "/mnt" share both on host and container path.

In NextCloud, enable "Apps" - " External storage support". Then in "Settings" - "External storages", add external storage of type "local". Give the Folder a name, and in in the "Configuration" textbox you type the mount, like "/mnt/user/Stuff". Without the quotes of course.

Awesome work jbartlett! It is now detecting all of my drives. One bug I've noticed is that if I attempt to start a benchmark on an individual drive, every drive is benchmarked again. Thank you for all your hard work.

I'm almost certain you've got some form of memory sparing turned on. I had this exact same issue when I first got my Supermicro board and it took quite some Bios searching to disable the memory sparing feature. Normally those numbers should be the same or just about the same. The percentage of memory used (61% in your case) is 61% of allocated memory (8GB) - you can verify this is correct by typing: free -h on the command line.

Not 100% true. You can always look at the commit history on GitHub for the webUI to see what's coming at least in the UI itself.

You would have to provide more details before we could analyze the specific situation to determine whether those things I mentioned are not coming into play. Split Level can force unRAID to put a file on a disk other than the new disk. And 0 Minimum Free is not recommended and is probably one of the main reasons people get unexpected out-of-space. unRAID has no way to know how large a file will become when it chooses a disk to write. If a disk has less than Minimum Free, it will choose a different disk. You should set Minimum Free to larger than the largest file you expect to write to the User Share. There is also a Minimum Free setting for cache in Global Share Settings. But as I mentioned, Split Level takes precedence, so if Split Level says a file should go on a certain disk to keep it together with other files, then that is the disk it is going to choose.

Binhex's rTorrent VPN docker has the ability to enable flood already, I use it personally and like it well enough. One of the docker arguments is "enable-flood" and once set to yes will enable the flood web interface on port 3000.

Just commenting here because I would still be very interested in an unRAID Collabora template. Can't seem to get it working with reverse proxy despite following instructions linked above.

Or get them to use an online tool like this and send you the output....