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

ColdShoulderMedia · 3. März 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 · 3. März 2023

Zitat von 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.

Zitat von 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 · 3. März 2023

Zitat von 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 · 3. März 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

Beitrag

RE: AdGuard-Home

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

(Quelltext, 20 Zeilen)

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…

raulfg3

10. Dezember 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 · 3. März 2023

Zitat von 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 · 3. März 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 · 3. März 2023

Zitat von 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 · 3. März 2023

Zitat von 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?

Zitat von chente

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

Are compose yamls kept in the containers themselves?

Zitat von 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 · 3. März 2023

Zitat von 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.

Zitat von 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 · 3. März 2023

Zitat von 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 · 3. März 2023

Zitat von 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 · 6. März 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 · 6. März 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 · 6. März 2023

Zitat von 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 · 6. März 2023

Zitat von 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!

Jetzt mitmachen!