Finally, there is an official Joomla (4.x) Docker made for unRAID. But it is not done well. As in, you will lose all your settings and data when you restart your docker. So you need to copy the data outside the docker into the appdata folder. (Or wherever you want it)
Inside the docker image, the Joomla folder resides here:
/var/www/html/
And this is the folder you need to make “external” by adding a path to the edit/install panel.
This of course, made me extremely nervous. Luckily this only meant that my docker file got corrupted. It happened most likely while I was moving it while the docker service was still active. Yeah, it happens.
Solution:
It’s fairly simple, but it takes a little bit of time.
Go to Settings -> Docker -> Enable Docker, and set to No, then click the Apply button (this disables Docker support)
Go to the location of your docker image and rename the file to docker.img.bak – The file may be in
/mnt/user/system/docker
I’m asking you to make a backup, because in all cases, safety first. “Why didn’t you have a backup in the first place?”, I hear you say. Yeah yeah, we all make mistakes every so often! D:
Go to Settings -> Docker -> Enable Docker, and set to Yes and this creates a fresh and empty Docker image. The docker service should now be started. You can see this as this on the docker settings page:
and on the dashboard you should now see an empty docker field.
Now go to the Apps Tab, Previous Apps Section. Then check off all of your previous applications and hit “Install”
I recommend to do it one by one so you can double-check the settings and clean up the unused templates after you’re done. If you want to make a copy of the templates, FTP into your server and go to
/boot/config/plugins/dockerMan
After you have restored your docker apps, you’re done. Check all the things and make a backup 😉
Due to CONTINUOUS database corruptions I was forced to downgrade my unRAID back to 6.6.7 to see if that fixes the corruption issue. It’s really terrible and apparently hard to fix because LimeTech has not fixed the issue yet, not is is acknowledged as an issue.