As I was following the previous guide in order to have omv6 on a flash drive, docker on an SSD, and my data on a 6TB HDD.
The "previous" guide still exists. It's here and it's already updated. https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv
you have a procedure here https://wiki.omv-extras.org/do…openmediavault-compose_67
and a guide here Guide: Using the new docker plugin
that explain what you need. Have you read them?
I looked at the thread, i didn't read specifically those pages (which are easier to read), but the informations are the same.
My thoughts presented in my previous post are what i understood of the update, i just wanted to confirm i understood correctly.
I would like to add that the previous guide was very easy to follow for someone with my experience level--none. 
i just wanted to confirm i understood correctly.
You understood correctly.
I found your newly written guide and reviewed it. Thank you and everyone for the efforts! As I was following the previous guide in order to have omv6 on a flash drive, docker on an SSD, and my data on a 6TB HDD. You introduced the name containers. You seem to say that should go on the HDD. Is that the same as the DATA in the previous guide? It would be helpful to have some consistency for those of us with only a limited knowledge and trying to follow something. Could someone possibly look at the previous guide and get us to the endpoint of loading a container with jellyfin, using the naming convention used in the previous guide. Thank you 🙏!
You can name it anything you want. I try not to name critical folders after service names, etc.. as I've found from helping very new users, it results in confusion.
I'm not familiar with the guide you're looking at , but what are you trying to do? The name of the folder isn't really relevant, the key is that it is on a drive other than the your flash drive (SSD, data drive, whatever).
as I've found from helping very new users, it results in confusion
Well I think this is not correct. On the contrary, I think that naming the folders helps to keep track of the explanations, especially with new users. But everyone has their way of explaining things, it's like Linux, there are infinite ways
Edit - found solution.*
First - I appreciate both the thread and the amount of time taken to recreate the plug-ing, the capability, and answer all the panicked users.
Bottom line up front:
Problem: the new instructions at https://wiki.omv-extras.org/do…cker_compose#installation state to first install the Docker Repo from the omv-extras before the Compose plugin. Somewhat similar to before.
--However, you can't click the "Save" button until AFTER you install the OMV-compose.
Wrong. However - *you can't click the "Save" button until after you deselect the yellow check-box for Docker repo and the re-select the yellow check box.
Once you install the Docker repo, the OMV-compose URL is accessible.
--Further however... the OMV-compose relies on Docker installation to work
---Further however... the above is an assumption as I get the big red error box upon trying to install the OMV-compose, but the key error line is not that Docker isn't installed it is this:
Err:1 https://openmediavault-plugin-developers.github.io/packages/debian shaitan/main amd64 openmediavault-compose all 6.7.4
404 Not Found [IP: 185.199.108.153 443]
So I think the correct order should be :
1. OMV-Compose (where presumably I'll be able to choose the Docker install location...?)
2. Docker repo
But until the URL https://openmediavault-plugin-…github.io/packages/debian works, not sure we can do anything.
The "previous" guide still exists. It's here and it's already updated. https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv
Step 4 in the guide is still incorrect. It does not reflect the new way docker is found unless your link is linking me to an old version.
Err:1 https://openmediavault-plugin-…github.io/packages/debian shaitan/main amd64 openmediavault-compose all 6.7.4
404 Not Found [IP: 185.199.108.153 443]
Your package cache is old since I just release 6.7.5. Click the apt clean button in omv-extras.
Well I think this is not correct. On the contrary, I think that naming the folders helps to keep track of the explanations, especially with new users. But everyone has their way of explaining things, it's like Linux, there are infinite ways
I dunno, maybe the folks I've helped were "extra special" ( Nick0 ..lol) but Iv'e seen this confusion multiple times. That's why I got away from calling it docker (I used to call it docker as well)
It is showing the docker, portainer, yacht version. The instructions do not work at that point. Thanks!
tep 4 in the guide is still incorrect. It does not reflect the new way docker is found unless your link is linking me to an old version.
The screenshot is old but the method is correct. Although there is little reason to click the reinstall button (unless you changed the docker path). Setting the shared folder for the compose files will ensure that docker is installed and configured when you click Save and Apply.
maybe the folks I've helped were "extra special"
Probably...
I have about 20 containers running. I've already backed up the folder where I saved your settings (in case I need them) and your individual docker-compose.yml files. The whole migration process doesn't seem to be complicated, just laborious, depending on the number of containers. My question is about the usability of Portainer after the migration. From what I understand the containers created by Portainer will not appear in the plugin and vice versa, right?
I have about 20 containers running. I've already backed up the folder where I saved your settings (in case I need them) and your individual docker-compose.yml files. The whole migration process doesn't seem to be complicated, just laborious, depending on the number of containers. My question is about the usability of Portainer after the migration. From what I understand the containers created by Portainer will not appear in the plugin and vice versa, right?
Containers created in Portainer, will not appear in OMV.
Containers created in OMV, will show in Portainer... but you will have limited management of them (you'll basically be able to start/stop them)
Sorry but how do I set the drive where docker is supposed to be loaded to if I can't see it? The wiki guide says it will not go to the correct place if it is not set there.
Your package cache is old since I just release 6.7.5. Click the apt clean button in omv-extras.
FWIW, the "issue" with the Save button being grayed-out by default remains even after the apt-clean and GUI refresh. Even tried a restart just to check.
Not a big deal, but you do have to de-select the yellow button for "Docker repo" and re-select before Save is accessible.
Perhaps not having the Docker repo check-box pre-selected?
Or just one line on the instructions page telling people to de-select the button first:
But it isn't a substantial change. It is moving components from one plugin to another. I will admit that we need to improve the docs since people are having issues but I struggle to understand the noob thinking well enough to write those docs.
I would love to know what you did because I am guessing you clicked the Reinstall docker button? I had a note that it was only needed if docker was not already installed. I bolded that note. Otherwise, all of these changes would NOT touch your existing docker containers and moving portainer to docker-compose control would only take down portainer and NOT other containers.
If you use the portainer-omvextras example as I mentioned in the first post, your portainer should just come back and you can start your stacks again. nothing should be lost unless you did something else.
Duly noted - thanks for taking the time to reply.
Here's exactly what I did:
Step 4 in the guide is still incorrect. It does not reflect the new way docker is found unless your link is linking me to an old version.
The screenshot is old but the method is correct. Although there is little reason to click the reinstall button (unless you changed the docker path). Setting the shared folder for the compose files will ensure that docker is installed and configured when you click Save and Apply.
I forgot to update that screenshot, it's fixed now.
Sorry but how do I set the drive where docker is supposed to be loaded to if I can't see it? The wiki guide says it will not go to the correct place if it is not set there.
Once you install the Docker repo, and then the OMV-Compose plugin you will have to actually install Docker from the Services-> Compose section.
In there, Under "Settings" you set both the Compose folder and the Docker install folder. Save, then Install Docker.
Don’t have an account yet? Register yourself now and be a part of our community!
