terratrax

Yep this will work - or you can use the :testing tag which will be version 30 in this case. Going forward, each new version has its own unique tag so you should be able to upgrade in sequence. If you are using :latest and your version is still showing 29, my guess is that unraid has not pulled the latest image and you might need to check it manually.

Hi Saarlaender - I'm not sure I understand your question but the best place for these types of questions in probably in the main Nextcloud support thread. This image is basically the stock image with some libraries added to support Memories; everything else is untouched.

The latest tag has been updated to Nextcloud 31.0.4. You can also use the tag 31.0.4-apache if you don't want to automatically get updates.

Regarding GPU support it is not built into this image as this is quite a bit more involved than just updating the docker image (there are things you would need to do on the host). Honestly however there is not much benefit - yes memories can take a little longer to index the first time around but after that the CPU should be able to keep things up to date without any lag.

The git repo with the description has been updated, but I have no idea how often the unraid site polls it for updates.

Image updated to 30.0.5

Glad to hear it! I can't speak to the HDR function unfortunately. I don't write the code for memories, just providing the libraries it needs.

I'm not running into the same issue. Can you try to run the scan via occ and paste the output?

I'm guessing you solved this already but the permissions on the unraid side of things for the mapped volume need to permit UID 33 (www-data inside the container).

Hi - for support not specific to the changes this image adds (bzip, pdlib, ffmpeg, etc.) please see the main Nextcloud thread as they will better be able to support you. As mentioned many times in this support thread this image is 99.9% stock and works like stock, it just has a few extra libraries installed.

I dropped the 29.0.2 image today 🙂. Should be on docker hub later tonight!

As you can probably see from the comments above, this image is still maintained, but given that it is 99.9% the stock image (just with a few libraries added) from Nextcloud, you're probably better off trying to get support in those forums. That said, mapping the data folder is a hard requirement - if you haven't provided storage for the container it's unlikely to start.

Yes, but probably after a couple of months. I tend to like major releases settle and all the apps get the kinks worked out before I update the image. I haven't tested so it's hard to say how much effort it will be. You can try updating the base images in the dockerfile and building the image yourself though if you are in a rush!

Done! (27.1.6 actually)

Hi Herbert, This container image is 99% the stock container image that is maintained by Nextcloud. The only difference is that I have added some libraries to let the facial recognition add-ons work properly. For questions like this, you would probably be better off in the Nextcloud support forum. I think you will find the answer actually with a little searching - it is most likely caused by your reverse proxy or firewall flattening all requests to the same IP address. So invalid attempts from bots get counted against your IP.

Hi Shawn! With the exception of a few libraries to enable you to run face recognition and a few other multimedia plugins, this is the standard Nextcloud docker image. There are very low level additions that do not change the way you operate the software. The advantage of this is that you can seek support from the huge base of users Nextclouds docker image has. I would bring your question about the crontab there, but I'd think you can just install crontab using the package manager if you need it. For questions on how to use the recognize or memories apps, you'll have far better luck asking these questions in their respective support forums. The types of questions appropriate most for this forum would be system errors due to missing libraries, requests for additional or update libraries, etc.

It was released a couple of days ago actually.

This is usually caused by incorrect permissions in the dockers appdata folder. Whatever UID you have the container set to run with needs write access to this folder (within appdata). Should be a pretty easy fix!

Sorry if I wasn't clear but I'm not planning to release an image with self-signed SSL because it would require some pretty significant changes to the official Nextcloud image which I'd like to avoid. Also with Letsencrypt and things like NginxProxyManager, you can get real, signed certs for free instead of using self-signed ones. Id highly recommend checking these out if you are familiar with them.

Linuxserver uses their own alpine linux image and fpm to host nextcloud as opposed to this image which is Nextclouds official docker image with some added libraries. This is not to say it wouldn't be possible, but right now anyone that uses this image can 100% rely on Nextcloud documentation and I'd like to keep it this way.

Hi and thanks for your effort but it was sorted out already - I like to let new images bake in my environment for a few days (I keep good backups) before I push an image.

Hi all and sorry for the delay - this was one of those things where upgrading one thing broke another and so on. It just took some sitting down for a few hours to work through it all and then some more time testing to make sure the image worked in my environment. New image is up with updates dlib, pdlib, and of course Nextcloud 27.1.4!

There were some incompatibilities with the base image a couple of revisions ago that made this impossible or difficult. Let me give it another go, will update within the next week!

If you already have Nextcloud installed using the stock image then you shouldn't need to delete it. Just change the image and you should be good to go!

Hi Goldbondx, you might try the regular support forums and see if they can help on the front end of the app. The only difference between this docker image and the stock one for version 26 is the addition of the libraries needed for the facial recognition apps, which sounds like are working OK so my guess is that it has something to do with the Recognize plugin configuration itself, of which I'm not an expert unfortunately!