Use custom redis image for Nextcloud AIO

🚧 Installation
1

How can i make Nextcloud AIO use my self build redis image because currently i cant get nextcloud to use that everytime it just overwrites my Image with its own. My redis image is a modified Version of the nextcloud-aio-redis one i overwrited the image of nextcloud aio with my own and the same name and tag but every time i try to start the containers via nextcloud aio it just overwrites my image. My Redis image just adds a Config file to skip the ARM_COW_BUG check because this check can’t be performed on my System (The System itself has this patch)

So if anyone knows how i would appreciate that

2

You should give your image another tag. Same name but other tag, e.g mine

Then you should see something like in this example:

~# docker images | grep redis
nextcloud/aio-redis         latest    7af844ef1366   2 months ago   43.6MB
nextcloud/aio-redis         mine      b164ad7bc047   1 day ago      43.7MB

Then you must edit this line in your master container:

This is the command to edit that file with the editor of your choice:

editor=nano # change this to the editor of your choice, e.g joe
sudo docker exec -it nextcloud-aio-mastercontainer bash -c "apk add $editor; $editor php/containers.json"

So this:

      "container_name": "nextcloud-aio-redis",
      "image_tag": "%AIO_CHANNEL%",
      "display_name": "Redis",

should look like this:

      "container_name": "nextcloud-aio-redis",
      "image_tag": "mine",
      "display_name": "Redis",

after you edited it.

Then stopp all containers from within the AIO Interface and start them again.

These changes are not permanent, so you’ll have to do it again after every update of the master container.

However, if it works well and your change can be turned on/off with an environment variable, you could suggest including it in the code. Either by creating a PR or getting someone with knowledge to do it. After that, you can rightly say that AIO works on OpenWRT!

Much and good luck,
ernolf

3

OK thanks i did it a little diffrent but its basicly the same and it works but all containers are stuck at starting even so the database is clearly running (maybe some other OpenWRT bug) Thanks for the Reply