What are the Best Practices for moving from 4 to current build (6)

ColdShoulderMedia · Mar 3rd 2023

I think it's finally time to upgrade my system and move from 4.1.36-1 to the latest stable build. This leads me to some questions, but please point out if I'm missing any information.

Most of my concerns are related to docker, I'm not very knowledgeable on the subject and the progress I have made was mostly stumbling through TechnoDadLife OMV tutorials for 4.x. As such, I've just only really used the GUI, so my understanding of docker structure is tenuous.

So the big question is, is it best practice to upgrade or do a fresh install?

And if I am doing a fresh install, is there a way to bring my docker instances with me?

chente · Mar 3rd 2023

Quote from ColdShoulderMedia

is it best practice to upgrade or do a fresh install?

The only way to upgrade from 4 to 6 is to upgrade from 4 to 5 and then from 5 to 6. It's a long road and there will probably be problems. The end result may not be as expected.

I wouldn't hesitate to do a fresh install.

Quote from ColdShoulderMedia

is there a way to bring my docker instances with me?

Regarding the containers, it will depend on how you configured them. I could count on one hand the Technodad tutorials I've seen.

Here is a simple procedure that works for using docker. [How to] Docker in OMV

raulfg3 · Mar 3rd 2023

Quote from ColdShoulderMedia

And if I am doing a fresh install, is there a way to bring my docker instances with me?

+1 for a new fresh install.

Regarding dockers apps, lots of then do not save critical info, so not a problem to recreate it from scratch eg: pihole, transmission, etc..., others like plex have a big database that you can recreate, but is better to try to preserve, in that case you only need to copy the config of that dockers, and recreate the new ones pointing to that previosly saved config, problems expected are permission/owners, so unless you realy need to preserve, most cases are quickly to start from scratch.

raulfg3 · Mar 3rd 2023

deploy a docker using portainer is really easy, you only need the file.yaml and deply the stack on portainer.

some examples: RE: Scrutiny - a new open source S.M.A.R.T. monitoring web UI

Post

RE: AdGuard-Home

this is my working adguard.yaml file to install from portainer stack:

(Code, 19 lines)

You need to see the videos to understand how to create MyMacVlan on portainer webGUI prior to deploy.

on my stack 192.168.1.3 is the Ip of adguard.

first time, yo nee to connect to 192.168.1.3:3000 as is described on https://hub.docker.com/r/adguard/adguardhome to configure your adguard to work.

Once configured , you can login in adguard webGUI on 192.168.1.3

Please change 192.168.1.3 for your desired DNS server…

raulfg3

Dec 10th 2022

And you only need to save in a safe place this file.yaml to have a backup of your dockers and deploy it in a easy way on other NAS.

chente · Mar 3rd 2023

Quote from raulfg3

And you only need to save in a safe place this file.yaml to have a backup of your dockers and deploy it in a easy way on other NAS.

openmediavault-compose does it for you.

ColdShoulderMedia · Mar 3rd 2023

I'm sorry if these are obvious questions.

So are the docker instances that I'm currently running through the OMV-docker-GUI saved as docker compose files? Is there a way I can easily save/read them to reference while setting up new containers? Or can I just transfer over the compose file (or equivalent)?

chente · Mar 3rd 2023

Quote from ColdShoulderMedia

So are the docker instances that I'm currently running through the OMV-docker-GUI saved as docker compose files?

I'm not sure but I would say no. There probably isn't a docker-compose yaml file in those containers.

How many containers do you have? Which are?

ColdShoulderMedia · Mar 3rd 2023

Quote from chente

I'm not sure but I would say no.

I had assumed the OMVdockerGUI saved a compose-like file somewhere which it referenced while starting containers, is that not the case? Your response reads to me as though the GUI starts container instances with varying methodology, is that correct?

Quote from chente

There probably isn't a docker-compose yaml file in those containers.

Are compose yamls kept in the containers themselves?

Quote from chente

How many containers do you have? Which are?

linuxserver/swag and some media/game servers: jellyfin/jellyfin, linuxserver/airsonic, itzg/Minecraft. There are 10 active containers as of now.

chente · Mar 3rd 2023

Quote from ColdShoulderMedia

I had assumed the OMVdockerGUI saved a compose-like file somewhere which it referenced while starting containers, is that not the case? Your response reads to me as though the GUI starts container instances with varying methodology, is that correct?

There are two ways to deploy a container, from the CLI with commands or with docker-compose and a yaml file. I think I could put my hand in the fire and I wouldn't get burned if I say that your containers are implemented by the OMV4 plugin with CLI commands. Therefore you will have to recreate them again.

Quote from ColdShoulderMedia

linuxserver/swag and some media/game servers: jellyfin/jellyfin, linuxserver/airsonic, itzg/Minecraft. There are 10 active containers as of now.

The case of Jellyfin is simple, in the guide that I said in post 2 you have an example for Jellyfin.

Others like Swag I suppose you will have to redo configurations depending on the services you use.

As for game servers I can't help you much.

gderf · Mar 3rd 2023

Quote from ColdShoulderMedia

So are the docker instances that I'm currently running through the OMV-docker-GUI saved as docker compose files?

No.

But you can try to create compose yml files from running containers. I can't speak to whether the resultant files will work or not though - I have never tried using them. They do look quite a bit verbose, compared to the minimal ymls I use here. Worth a try.

GitHub - Red5d/docker-autocompose: Generate a docker-compose yaml definition from a running container

Generate a docker-compose yaml definition from a running container - GitHub - Red5d/docker-autocompose: Generate a docker-compose yaml definition from a…

github.com

chente · Mar 3rd 2023

Quote from gderf

But you can try to create compose yml files from running containers. I can't speak to whether the resultant files will work or not though - I have never tried using them. They do look quite a bit verbose, compared to the minimal ymls I use here. Worth a try.

Seems like a good way to go. Nothing is lost by trying.

ColdShoulderMedia · Mar 6th 2023

Thank you for directing me to that script, I've pulled all my current dockers through that autocompose.py. I do not intend to use them directly, but having them as reference while configuring new instances through the new docker environment will be very helpful!

gderf · Mar 6th 2023

You could try using those generated compose files and see what happens. OMV 6 has the openmediavault-compose 6.6.1 plugin which allows one to import compose files.

ColdShoulderMedia · Mar 6th 2023

Quote from gderf

You could try using those generated compose files and see what happens. OMV 6 has the openmediavault-compose 6.6.1 plugin which allows one to import compose files.

I could, but at this point I would like to be a "big boy" and actually learn how Docker and my containers work instead of just limping along in someone else's wake. Still, these compose files will act as an effective guide as to what I should end up with. Thank you!

auanasgheps · Mar 6th 2023

Quote from ColdShoulderMedia

I could, but at this point I would like to be a "big boy" and actually learn how Docker and my containers work instead of just limping along in someone else's wake. Still, these compose files will act as an effective guide as to what I should end up with. Thank you!

If you do - and it's definitely worth it - there are tons of guides, here on this forum and on YouTube.
Docker is widely popular, and you just need to find the way that suits you.

You'll get used to Yaml's compose files, they are divided in sections and there's always a template made by somebody else, most of the time you'll just need to adjust ports and file paths.

And you can always ask for more help!

omv_ross · Jul 18th 2024

Update / Upgrade problems / login problems.

Gracious good day! I'm a full on noob that followed a DIY to setup OMV on an RPi4 a few years ago. It was very much a 'set & forget' thing as it's been so maintenance free. Yes I'd log in to OMV control panel to setup redundant backup to a 2nd external hd (14Tb) ... which was setup thru OMV control panel. I have two questions:

1. Somehow, my password to access OMV control panel from browser doesn't work anymore... I gots no clue how this happened because it's straight cut & paste from my KeePass password manager...help!

2. Is there a best practice for a noob like me who just wants a stable NAS... ie. a 'stable' upgrade path that doesn't risk breaking everything. Up until now, about every year or so, I'd log into RPi4 and do the ol': sudo apt update / upgrade / dist-upgrade and pat myself on the shoulder believing that I've done something proactive to maintain health of server; but honestly I have no clue. I went to update today and I got the following message after sudo apt upgrade:

Reading package lists... Done

Building dependency tree

Reading state information... Done

Calculating upgrade... Done

The following packages will be upgraded:

bind9-host bluez less libbind9-161 libdns-export1104 libdns1104 libglib2.0-0

libglib2.0-data libisc-export1100 libisc1100 libisccc161 libisccfg163

liblwres161 nano php7.3-bcmath php7.3-cgi php7.3-cli php7.3-common

php7.3-fpm php7.3-json php7.3-mbstring php7.3-opcache php7.3-readline

php7.3-xml python3-idna

25 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Need to get 12.3 MB of archives.

After this operation, 34.8 kB of additional disk space will be used.

E: You don't have enough free space in /var/cache/apt/archives/.

... any help toward a clear update and maintenance path / schedule would be greatly appreciated.

ryecoaaron · Jul 18th 2024

Quote from omv_ross

omehow, my password to access OMV control panel from browser doesn't work anymore... I gots no clue how this happened because it's straight cut & paste from my KeePass password manager...help!

sudo passwd admin

Quote from omv_ross

Is there a best practice for a noob like me who just wants a stable NAS... ie. a 'stable' upgrade path that doesn't risk breaking everything. Up until now, about every year or so, I'd log into RPi4 and do the ol': sudo apt update / upgrade / dist-upgrade and pat myself on the shoulder believing that I've done something proactive to maintain health of server; but honestly I have no clue. I went to update today and I got the following message after sudo apt upgrade:

Yep, you should upgrade to the last stable version of OMV more often instead of waiting every few years.

There are threads about going from 5 to 6 to 7. I recommend freeing up space before doing that. This thread will help [How-To] Fix full OS filesystem - GUI login loop

omv_ross · Jul 27th 2024

Thank you for your response. df reports 100% /dev/root usage (14971044 of 15096752 1K blocks). I couldn't succeed in navigating with cd / to /dev/root to investigate further. Apparently I'm running OMV 5.6.26-1. I tried changing admin password with your advice: sudo passwd admin but I still can't log into OMV control panel from browser. Did a reboot of rPi... still no dice in logging in to omv control panel. Worth noting my NAS setup here: I have external 14TB (spinny) drive with a second redundant 14TB (spinny) drive in some kind of recommended RAID arrangement. Wondering if best to bump current NAS data (i still somehow have access) to other devices and do a fresh install of OMV 6...whaddya think? If you agree, please advise best path to do so; as well as a timeline maintenance path moving forward so I can avoid these pleasantries in the future. Alternatively advise repair path. Gracious thanks for your assistance.

Soma · Jul 27th 2024

Quote from omv_ross

I couldn't succeed in navigating with cd / to /dev/root to investigate further.

Read the linked thread properly to figure out what is filling up your root drive

omv_ross · Aug 3rd 2024

Hello. As I mentioned previously, I can't navigate to /dev/root. the best I can do is navigate to /dev and in there 'ls' lists many items but root isn't one of them. While in /dev I enter: du -xhd1 which gives me a list of about 10 items (all numbered '0') and beside this column of zeroes is ./v4l and next: ./dri and next: ./disk and next ./block. So I'm stuck there while following thread (fix full OS -GUI loop) you mentioned. Any advice?

Worth noting that at this point I can no longer access my 14TB drives with data on them

Thank you for any suggestions

Participate now!