Finally I moved all the containers, even though I didn't have the yaml files. Now everything is simpler and more effective. Thank you all for your support and for evolving and improving OMV with this update.
So how did you do it without the yaml files to get all your configs back for each of your Docker applications? Or did you start from scratch?
Added in the docker-compose wiki document the procedure:
How to recover Portainer and other containers from versions prior to omv-extras 6.3 / openmediavault-compose 6.7
Thank you very much for this addition. This is very helpful and will hopefully mitigate the stress for OMV hobby admins (regarding as it was noted in this post (average users, majority of user etc.: RE: omv-extras 6.3 / openmediavault-compose 6.7) with this upgrade or improvement.
Hello there,
I am a long time member here and unfortunately I was also hit by this update or improvement. So I understand the rational behind it and I am very thankful for the work of ryecoaaron I really would love a bit more smoothness in such an update. Especially thinking about the league of hobby OMV admins which struggle now as we see in thread, with the new way the docker and portainer things go.
You are not alone with that mess and with that question. And yes, I also wonder how that could happen.
Hi there,
aah, that is not what one intends with a fix of another problem...
However, you may want to try this:
1. Remove docker
2. Remove portainer
3. apt-clean in OMV extras settings
4. reboot
5. apt purge apparmor apparmor-utils
5. reboot
6. Apply this fix in the grub conf.: RE: docker not working since omv-upgrade
7. reboot
8. install docker
9. install portainer
Out of nothing I had the same issues after updating to the newest OMV and docker version via OMV update. I had to:
1. Remove docker
2. Remove portainer
3. apt-clean in OMX extras settings
4. reboot
5. apt install apparmor apparmor-utils
6. install docker
7. install portainer
Then, the portainer/docker combo worked again.
Well, being clear and concise in the GUI is always better than taking assumption that the user will That might be the case for tech-savvy user which will also have not problems to work with 1 to n test systems in a virtual machine or elsewhere. However, for the not that tech-savvy part of the OMV users, and they are still addressed with OMV 6, being more descriptive in the GUI is an added value. So I would like to second the suggestion of monsen to add a small descriptive text.
Hi there,
choosing a more or less 1:1 replacement for PhotoStation is for me a daunting and yet still unfinished task ... I also looked at the XPENOLOGY solution but then I decided that I am not brave enough for this task.
So I want two add two more products I have tested and which might be of interest:
PiGallery 2: a self-hosted directory-first photo gallery website which works x86 and Raspberry Pi , see http://bpatrik.github.io/pigallery2/ and https://github.com/bpatrik/pigallery2 . It is actively maintained and might be an replacement for PhotoShow.
PhotoPrism: an AI-powered app for browsing, organizing & sharing your photo collection. see https://photoprism.app/ and https://github.com/photoprism/photoprism . Photoprism will, depending on the settings you decide, also respect and work with a given directory structure.
Hi there,
version 5.1.9 fixed the issue on my system:
autoshutdown-restart is now set executable
Autoshutdown plugin works fine now 
Thanks all for helping to fix this issue.
Hi there,
thanks for the new version. I just updated to version 5.1.8:
autoshutdown-restart is removed from /usr/lib/systemd/system-sleep
autoshutdown-restart is installed in /lib/systemd/system-sleep
But:
autoshutdown-restart is not set executable
So, I think it should be set to executable for working correctly. Perhaps any insights on this by the experts? Thanks in advance.
Hi there.
as suggested in posting#3 (from nrand )I tried moving usr/lib/systemd/system-sleep/autoshutdown-restart to /lib/systemd/system-sleep/autoshutdown-restart and made autoshutdown-restart executable and now it works again. Thanks all in this thread for the help..
Hi there,
I observe exactly the same issue as gadric describes it. I am also a long time autoshutdown user without any flaws until version 5.1.7..
What I analyzed
/usr/lib/systemd/system-sleep# ls -l
-rw-r--r-- 1 root root 839 Jan 19 15:13 autoshutdown-restart
-rwxr-xr-x 1 root root 399 Sep 30 17:53 openmediavault-watchdogSo it seems that autoshutdown-restart is not (no more?) executable.
I tried this:
usr/lib/systemd/system-sleep# ls -l
-rwxr-xr-x 1 root root 839 Jan 19 15:13 autoshutdown-restart
-rwxr-xr-x 1 root root 399 Sep 30 17:53 openmediavault-watchdogbut without success. Making autoshutdown-restart executable does not solve the issue for me. Perhaps someone has another hint?
So getting in to the Docker and Portainer story is somehow daunting, especially for the average user I think. And yes the plugins have been much more intuitive and comfortable and felt somehow system-integrated. But, the OMV-extras project is short on developer and maintainer resources so the Docker/Portainer story is the best you can get at the moment and as said in this thread it is a good investment of your time.
Hi there,
I am wondering which is an easy and GUI based way to consistently backup and restore Urbackup backups and its corresponding database and configs to a cloud storage? Does someone have a solid and working concept on this?
Thanks in advance
Hi there,
indeed, it is a mess with this bootloader update.
However,
I also experienced this issue earlier today and used Boot-Repair-Disk to restore GRUB (which resolved this issue).
seems an easy approach to fix the wrecked system after you applied the the grub updated in question.
Hi there,
Heise Developer Online, a IT news site in Germany made some sort of summary and status of the boot loader mess which happens on different Linux distributions. So I wonder which is the recommended way to fix the issue on an OMV system? Is it the Boot-Repair-Disk or the rather complicated way as described by the Ubuntu Security Team ? Any advice by the OMV experts would be highly appreciated.
Hi there,
after applying these Debian 10 security updates
Get:1 http://deb.debian.org/debian-security buster/updates/main amd64 grub2-common amd64 2.02+dfsg1-20+deb10u2 [538 kB]
Get:2 http://deb.debian.org/debian-security buster/updates/main amd64 grub-pc amd64 2.02+dfsg1-20+deb10u2 [131 kB]
Get:3 http://deb.debian.org/debian-security buster/updates/main amd64 grub-pc-bin amd64 2.02+dfsg1-20+deb10u2 [903 kB]
Get:4 http://deb.debian.org/debian-security buster/updates/main amd64 grub-common amd64 2.02+dfsg1-20+deb10u2 [2477 kB]concerning the GRUB boot loader on my OMV 5 system I made a reboot and the I got stuck within the boot loader with this message:
error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue>
I suppose it has something to do with this Debian/Ubuntu Bug: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509
However, has anyone a hint to solve this issue?
Did you completely clear the Browser cache?
You may think about a Docker solution with NGINX like: https://hub.docker.com/r/linuxserver/nginx/ . So you do not have any trouble with the OMV web server and it is well documented and rather lightweight.
just a few comments on the products mentioned before:
- Duplicati slowness on larger datasets: I can confirm this from my test on OMV and Windows 10 platform
- Restic has a nice cross-platform GUI version, see the announcementin the Restic forum and more details from Relica
- Duplicacy has a nice cross-platform GUI version which resides "on top" of the CLI version
- GUI for Rclone: yes, the long awaited but unfortunately still in early stage resulting of GSOC project of last year I think. So I do operations on my cloud storage like delete files/folders, rename, make directory etc in a quick and reliable way with Cyberduck and hoping that Rclone finds a way to improve the GUI. I would not mind to pay for a GUI version of it so that also not that tech-savvy users could use it.