Ah I see, I understand that "DB" refers to database and that some dockers like Duplicati have them and therefore they should be backed up. I also have the docker override YAML backed up and was what I used to restore the containers so that they somwhat worked under DockStarter instead of compose plugin
Just not sure what other directories I should focus on
allways better rebuilt containers from scratch, you allways, can stopt then, copy DDBB or config and restart again eg: Plex or jellyfin, others no need it because no config or DDBB is nedeed
Sorry but what's DDBB and where should I do this from? These containers (and docker itself) can be seen from compose plugin as running but otherwise I have not set anything else for compose plugin especially its storage folders
Managed to use DockStarter (which was what I used in OMV6) to bring up the containers other than Portainer. Am encountering other issues regarding Duplicati and Transmission so it looks like I should just rebuild the containers
At least compose plugin can see the containers now. Should I export the settings using Autocompose, or just rebuild the containers from scratch?
It really helps that I do at least have some of the OMV installation backed up beforehand; just a matter of needing to know from where in the backup to use on the new containers
Thanks, but Portainer is down too now, no containers are running. Still trying to find out how I can get Portainer back up first
Hi, it's been a real long while! I decided to finally move on from OMV6 to OMV7 last night and it was pretty smooth once I got over a GRUB issue (specific to my setup; had to point this to my newer boot SSD instead of the non-existent older SSD) and another regarding the debain backports repo not being at the correct URL. Now mostly all good (even liked how SnapRaid now supports split parity, thanks again RyanAaron!)
Only problem I see is that all my Dockerised apps are not accessible. These were made during OMV5/OMV6 (yes this same setup is running since OMV5), using a guide here to set up DockStarter first and then Portainer. I understand that these are now no longer supported within OMV7 and I am to migrate them over to compose eventually. Just that I didn't have time for that until recently and all of them just worked during OMV6 before the move to OMV7 last night
Given that my storage devices are ok so far, I believe the apps, container files and settings should be somewhere in my setup.
May I know how I should find them and then migrate them over to the compose plugin? Thanks!
I tried to update Docker but I am seeing this unmet dependency "docker.io : Depends: runc (>= 1.0.0~rc6~)" in the logs
I have already tried omv-upgrade and dist-upgrade to no avail.
What should I try next?
Note that you need to do this for any changes to your SMB service (e.g. adding/removing a SMB share)
I worked around it by intentionally giving a short hostname, re-enabling SMB, and then changing the hostname back to what was set previously
I am having the same problem too and the script did not help
I'd suggest you ask at the dockSTARTer community. This does not seems specific to OMV.
Thanks, I asked as I wasn't sure if this is OMV + DockSTARTer specific, or just a general DockSTARTer "issue"
Seeing that the DockSTARTer docs mentioned that
ZitatDockSTARTer does not configure storage for you (you may use local storage, or cloud storage, multiple disks, raid, etc).
It sounds like it is working as designed; I am supposed to use overrides to "hard-configure" storage so that they can persist future compose runs.
Will put these links for future reference
https://dockstarter.com/overrides/introduction/
https://stackoverflow.com/ques…d-mount-and-managed-mount
https://devopsheaven.com/docke…es-in-docker-compose.html
EDIT: I managed to use overrides to override this issue. Marking this as resolved
You should spend more time on GH
Personally, I would not change a filesystem because of a certain mount point. There should be better reasons.
For me, it's more to do with taking this chance to jump over to a newer filestystem since I am already starting over with these newer HDDs compared to my previous setup
Apparently all I needed to do was to reset the state tables in my router, or simply just restart the router. I don't recall needing to do this the last time I needed to set up VPN in my router though...
That isn't going to happen in OMV 6. And I will definitely try to make a plugin to support ext4 if it does in OMV 7.
Thanks for all of your hard work by the way, your stuff is top-notch
I'd agree with the long term solution. Bearing in mind that as far as I know, in omv 6 btrfs will be the only officially supported filesystem. I'm guessing Aaron will come up with a plugin to support ext4, etc. as he has others.
My plan is to backup and go full btrfs at that time, but I will probably continue to use symlinks just in case something like this ever happens again. Plus, it also just makes it was way easier to remember my paths for docker, and it was dead nuts simple to set up.
Whoa, if this is true, is it a good idea for me to make the switch right now? The new HDD in question is going through badblocks to test that it works; I can always switch it to BTRFS instead of EXT4 once this is done and start testing if this works with whatever apps I am using
Is the new HDD formatted as btrfs or ext4? btrfs should still recognize labels.. ext4 is the issue. So if it is blank you can try reformatting it as btrfs and see if that helps.
You could always go to symlinks, and then just make adjustments to your current docker containers.
Thanks! All of my HDDs, new and old, are formatted as EXT4. One of them was before 5.5.20 while the other was done after 5.5.20. This would mean that it is working as intended and therefore I should consider using symlinks like what you have already done.
As for BTRFS, this seems more like a long term solution for me as I do indeed want a more robust filesystem like ZFS but simply do not have the hardware for it just yet. Is BTRFS stable enough even for production? Last time I heard it is not recommended (ZFS was promoted as the more stable solution instead)
I am affected by this change too even though I don't use said USB enclosures
I have one SSD and two HDDs. The SSD is by id while the first HDD is by label. The new second HDD is by UUID no matter if I had a label or not. I wasted about an hour trying to figure out if I need to modify fstab or simply relabel/remount/reformat the HDD until I saw this
Looks like I'll have to keep things in this uneven manner?
Was this after a reboot?
No, this happens only if I run DockStarter in command line and agree to compose the apps
First, which VPN you are using? Secondly, contact your provider, it will assist you in a better way.
I have followed their instructions to no avail
