omv-extras 6.3 / openmediavault-compose 6.7

Zitat von gderf

Every section of the forum has two pinned threads at the top related to your question. Have you read them?

I did but it doesn't help when I don't know what's gone wrong.

Zitat von jdavis739

I did but it doesn't help when I don't know what's gone wrong.

Exactly what is it you are looking for?

Zitat von ryecoaaron

I understand why the link works but you shouldn't have to do that. What is the output of:

ls -al /usr/local/share/compose/paperless/

sudo omv-salt deploy run compose

Thank you for trying to figure this out.

~$ ls -la /usr/local/share/compose/paperless/
insgesamt 28
drwxr-xr-x 3 root users 4096 16. Jun 16:29 .
drwxr-sr-x 4 root users 4096 16. Jun 16:38 ..
-rw-r--r-- 1 root root   351 16. Jun 14:50 docker-compose.env
-rw-r--r-- 1 root root   969 16. Jun 14:50 docker-compose.yml
drwxr-xr-x 2 nre  nre   4096 16. Jun 14:51 export
-rw-r--r-- 1 root users  351 16. Jun 14:30 paperless.env
-rw-r--r-- 1 root users 1042 16. Jun 16:29 paperless.yml

The yml was changed so recently since I had to upgrade to a hotfix release.

The output from sudo omv-salt deploy run compose looks unproblematic too:

----------                                                                                    
          ID: configure_compose_dir_paperless                                                 
    Function: file.directory                                                                  
        Name: /usr/local/share/compose/paperless                                              
      Result: True                                                                            
     Comment: The directory /usr/local/share/compose/paperless is in the correct state        
     Started: 21:43:07.840109                                                                 
    Duration: 13.68 ms                                                                        
     Changes:                                                                                 
----------                                                                                    
          ID: configure_compose_paperless_file
    Function: file.managed
        Name: /usr/local/share/compose/paperless/paperless.yml
      Result: True
     Comment: File /usr/local/share/compose/paperless/paperless.yml is in the correct state
     Started: 21:43:07.856334
    Duration: 65.389 ms
     Changes:   
----------
          ID: configure_compose_env_paperless_file
    Function: file.managed
        Name: /usr/local/share/compose/paperless/paperless.env
      Result: True
     Comment: File /usr/local/share/compose/paperless/paperless.env is in the correct state
     Started: 21:43:07.923365
    Duration: 72.599 ms
     Changes:   
----------

[…]

          ID: /usr/local/bin/docker-compose
    Function: file.symlink
      Result: True
     Comment: Symlink /usr/local/bin/docker-compose is present and owned by root:root
     Started: 21:43:12.741538
    Duration: 100.404 ms
     Changes:   

Hoping to see something more interesting I added the files anew as I did before. I was able to reproduce the issue but still nothing in the output of omv-salt:

----------                                                                                    
          ID: configure_compose_dir_paperless-error                                           
    Function: file.directory                                                                  
        Name: /usr/local/share/compose/paperless-error                                        
      Result: True                                                                            
     Comment: The directory /usr/local/share/compose/paperless-error is in the correct state  
     Started: 22:13:27.212446                                                                 
    Duration: 16.035 ms                                                                       
     Changes:                                                                                 
----------                                                                                    
          ID: configure_compose_paperless-error_file                                          
    Function: file.managed                                                                    
        Name: /usr/local/share/compose/paperless-error/paperless-error.yml                    
      Result: True                                                                            
     Comment: File /usr/local/share/compose/paperless-error/paperless-error.yml is in the corr
ect state                                                                                     
     Started: 22:13:27.229883                                                                 
    Duration: 63.408 ms                                                                       
     Changes:                                                                                 
----------                                                                                    
          ID: configure_compose_env_paperless-error_file                                      
    Function: file.managed                                                                    
        Name: /usr/local/share/compose/paperless-error/paperless-error.env                    
      Result: True                                                                            
     Comment: File /usr/local/share/compose/paperless-error/paperless-error.env is in the corr
ect state                                                                                     
     Started: 22:13:27.294952                                                                 
    Duration: 64.23 ms                                                                        
     Changes:                                                                                 
----------                                                      

But:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/usr/local/share/compose//paperless-error/paperless-error.yml' --env-file '/usr/local/share/compose//paperless-error/paperless-error.env' config 2>&1': Failed to load /usr/local/share/compose/paperless-error/docker-compose.env: open /usr/local/share/compose/paperless-error/docker-compose.env: no such file or directory

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/usr/local/share/compose//paperless-error/paperless-error.yml' --env-file '/usr/local/share/compose//paperless-error/paperless-error.env' config 2>&1': Failed to load /usr/local/share/compose/paperless-error/docker-compose.env: open /usr/local/share/compose/paperless-error/docker-compose.env: no such file or directory in /usr/share/openmediavault/engined/rpc/compose.inc:500
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatussN...', '/tmp/bgoutput7Y...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(503): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {main}

I recreated this issue with the same compose file I had used before and as I said, I ran into the same problem with another copied compose file. I tried to recreate it with another copied file though and this one worked like a charm. So maybe the error isn't with the setup but with these two files or the way I copied them.

Anyway, it works for me now and if anyone happens to run in the same issue they can create a link to fix it as mentioned above.

Zitat von aetherfaerber

The yml was changed so recently since I had to upgrade to a hotfix release.

How is the .env referenced in your yaml file for the one that fails? I ask because if you use a full file path it's not really allowed. The error message looks like it was trying to find a full file path in the folder where you have the compose file. From the docs:

Relative path MUST be resolved from the Compose file’s parent folder. As absolute paths prevent the Compose file from being portable, Compose implementations SHOULD warn users when such a path is used to set env_file.

Zitat von gderf

Exactly what is it you are looking for?

I can't figure out anything with OMV6. I've have to reinstall it 3 times because either it'll lock up and corrupt something or decide that it wouldn't update the files it needed. I just need portainer not this mess.

I'm done with OMV6 and going back to 5, if that causes any problems I'm done with OMV for good I don't have the time or patients to put up with this BS.

There were only two things I used OMV for macbook backup and portainer.

You aren't going to find a Portainer installer within OMV 6. That was deprecated. Install it by hand in the shell or use a compose file in the compose plugin.

Zitat von jdavis739

I'm done with OMV6 and going back to 5, if that causes any problems I'm done with OMV for good I don't have the time or patients to put up with this BS.

And go where?

"Because I have have been down there, I know that road, I know exactly where it ends."

I have tried every solution and OMV is still (on my hardware and experience) the smallest, fastest and most customized solution out of them at all and its a freakin NAS first. With an AMAZING support team on this forum. With NO COST to any of us.

Zitat von ED-209

And go where?

"Because I have have been down there, I know that road, I know exactly where it ends."

I have tried every solution and OMV is still (on my hardware and experience) the smallest, fastest and most customized solution out of them at all and its a freakin NAS first. With an AMAZING support team on this forum. With NO COST to any of us.

There is a big group of users who came down to OMV in order to have user friendly and easy setup of home made NAS. With a recent change of OMV extras, the task of setting up or migrating the previous containers became a daunting task.

The biggest problem is that OMV extras are developed/maintained by a single guy who is free to decide how and what he is going to support. If you read this thread carefully, the main reason he dropped portainer and yacht is because he doesn't like those anymore and doesn't want to support. This is not how you support your customers/users. We are not even given a choice to choose what we want to upgrade. The developer does not think about users and cares less if you had a working system and now nothing works. There are not so many proficient Linux users who are comfortable with all in depth linux command and configuring the system using command line. Majority of users are looking for simplicity.

I cannot rely on this system. I highly recommend you look at UNRAID OS system. I know it has some fee to it, but at least I did not hear anything like this happening. Another approach is to get a real NAS such as QNAP or Synology.

Zitat von juzzie

There is a big group of users who came down to OMV in order to have user friendly and easy setup of home made NAS. With a recent change of OMV extras, the task of setting up or migrating the previous containers became a daunting task.

The biggest problem is that OMV extras are developed/maintained by a single guy who is free to decide how and what he is going to support. If you read this thread carefully, the main reason he dropped portainer and yacht is because he doesn't like those anymore and doesn't want to support. This is not how you support your customers/users. We are not even given a choice to choose what we want to upgrade. The developer does not think about users and cares less if you had a working system and now nothing works. There are not so many proficient Linux users who are comfortable with all in depth linux command and configuring the system using command line. Majority of users are looking for simplicity.

I cannot rely on this system. I highly recommend you look at UNRAID OS system. I know it has some fee to it, but at least I did not hear anything like this happening. Another approach is to get a real NAS such as QNAP or Synology.

Not trying to fight, but there is a sticky about getting portainer working for you again. It literaly take 3 minutes to perform and you are completely back to portainer and all your containers are still there and still running. Nothing is lost. Have you tried that?

Like others, I have been down the road of commercial NAS boxes like netgear ReadyShare many years ago, a QNAP box, and other free NAS setups like NAS4Free/XigmaNAS and FreeNAS/TrueNAS. The commercial hardware nas boxes are not good. Then tend to be too limiting in my experience, but if you like to be told what to do and how to do it with little to no other choice, than they can work fine. The other free NAS softwares I mentioned are BSD based, and while under the hood BSD and Linux are very similar, and they are very stable and polished, once again there is a much more limited choice in what you can do with them because of that BSD backbone.

To me my choice came down to running Linux and setting up everything manually, or run OMV. OMV won because of it's lighter footprint compared to a manual setup.

Here's my story (i'm bad at English),

At first I also was freaked out! And started googling "omv alternatives" and got more freaked up!

Then I started trying to read the guide "Guide: Using the new docker plugin" on the omv forum. Then guess what? Within 35 mins of my precious time! I'm using the omv-compose plugin (tested 1 previous portainer stack). All my previous docker containers up and running with the previous portainer (which was already running). I've installed 2 more containers and planning to add more, as nothing has happened but good.

So when i see those kinds of bad comments, i get freaked out and ashamed thinking, if those lovely omv devs started to think, enough of this! And start using their time somewhere else, i or my kind of people will be dommed!

So, stop bitching and start reading (if you don't get it). And look in the mirror, and try to appreciate those developers for what they are doing for us (or for them as a hobby).

Or start paying, as some users commented, recommending UNRAID!

Zitat von dsm1212

How is the .env referenced in your yaml file for the one that fails? I ask because if you use a full file path it's not really allowed. The error message looks like it was trying to find a full file path in the folder where you have the compose file. From the docs:

Relative path MUST be resolved from the Compose file’s parent folder. As absolute paths prevent the Compose file from being portable, Compose implementations SHOULD warn users when such a path is used to set env_file.

ooops. I was about to say that the env-file was not mentioned in the yml at all but I rechecked this morning and it actually is mentioned. The problem is not an absolute path but the name docker-compose.env. Changed that and everything is fine.

Aaand while rechecking this I discovered the error I got for another package is indeed not the exact same error but something completely unrelated - although it looks quite the same in the omv gui.

Anyway, everything solved. It was just me not having a grip on the config files I'm using.

So again, everything I can contribute here is to say thank you for this plugin, I think it's great.

I also was confused by the dysfunctional omv-extras page but I just checked and the path from there is click "wiki", click one of the guides. That's not much really.

Zitat von juzzie

There is a big group of users who came down to OMV in order to have user friendly and easy setup of home made NAS. With a recent change of OMV extras, the task of setting up or migrating the previous containers became a daunting task.

The biggest problem is that OMV extras are developed/maintained by a single guy who is free to decide how and what he is going to support. If you read this thread carefully, the main reason he dropped portainer and yacht is because he doesn't like those anymore and doesn't want to support. This is not how you support your customers/users. We are not even given a choice to choose what we want to upgrade. The developer does not think about users and cares less if you had a working system and now nothing works. There are not so many proficient Linux users who are comfortable with all in depth linux command and configuring the system using command line. Majority of users are looking for simplicity.

I agree with what others have said, just spend some time reading the guides and watch the video, you'll be back to portainer in no time. I used to use both portainer and yacht, found portainer to be a pain to update, it SO much easier to pull new image and then click up, job done.

Regarding the developers, please remember they don't get paid for this. You could learn to program or write guides and help them out. I think toomany users forget that if the developers get cheesed off with loads of negative comments because people have been to lazy to read documentation, they might say 'stuff it' and go to another project and help there, or pack developing up altogether. I've not seen many problems not get fixed with help from developer or members of these forums. I think this is a really good Open Source project and hope it carries on for a long time.

Personally I don't use either portainer or yacht now, the plugin is a better solution as its built into OMV. I've been keeping an eye on Truenas scale and have seen loads of problems with it when it comes to docker containers, even though it has truecharts baked in.

I much prefer the docker-compose yml way of running containers rather than the truechart or UNRaid way of getting containers up and running, much more control and way easier to change values if need be.

Zitat

I cannot rely on this system. I highly recommend you look at UNRAID OS system. I know it has some fee to it, but at least I did not hear anything like this happening. Another approach is to get a real NAS such as QNAP or Synology.

For OMV was great because I could use JBOD for storage, and went from a low powered pc's to a AMD 5600g and 64G, which will be much faster than either QNAP or Synology, I also think OMV is more secure than QNAP, plus I see a quite a few problems with Synology and docker.

Also OMV has some good documentation and guides, and a good forum with a number of experienced members who answer questions in a good way, when compared to some other forums.

Of course you could just install Debian 12, add file sharing,docker and portainer and manage it all yourself, but it's so much nice to have a small system that generally 'just works'

Zitat von juzzie

The biggest problem is that OMV extras are developed/maintained by a single guy

Which is exactly why it is free.

Zitat

I cannot rely on this system. I highly recommend you look at UNRAID OS system. I know it has some fee to it, but at least I did not hear anything like this happening. Another approach is to get a real NAS such as QNAP or Synology.

I have tried Proxmox, ESXi, UNRAID, Ubuntu with OMV VM, Windows Server, BSD etc. This just works (especially if you are using it on a low resource machine like a pi?!??) The others all have some requirement that makes it off the list. Ram requirements, certain hard drives, more beefer system specs. At the end of the day it is what best suits you and your use case scenario. But to demonize something after an update. The BIGGEST issue is learning Linux. I was the same years ago, until I sat down and committed 1/2 a day learning commands and playing with different distros. Knowledge is power and you said it, Its a single guy responding to all the posts with help from some mods. Plus a day job and a personal life. If this was a product we bought I would absolutely demand more.

I don't mind, I suppose showing all running containers whether started from plugin or CLI using (docker container ps --all), would stop a lot of the accusations of containers going missing, when upgrading to Docker-compose plugin, especially as I expect there are quite a few systems still to upgrade.

I would like Services being in the menu before containers though.