Argon EON - OMV Version 6.5.7-1 (Shaitan) - Portainer not working

I am having trouble installing and using Portainer in OMV on the Argon EON NAS RasPi 4 8gig (It is not the ARGON case with the issue nor the Raspi! - it is OMV!)

I have the Argon EON NAS (a great unit but the fan is way too loud even after adjust the fan speed!) and OMV Version 6.5.7-1 (Shaitan) installed and I want to use docker / Portainer.

With this version of OMV, they have changed, for the worse, the way Docker and Portainer are installed.

There used to be a simple and working option under ‘OMV-Extras’ and it was a simple click to install both Docker and Portainer - bliss!

Now they have done away with that and it is a much more cumbersome process. You have to instal Compose/Files and use scripts to install any Docker containers. I find Portainer so much easier and simple to install Containers so I am trying to install that using a script following this YT video (rather than try to spell out the steps here).

I am trying the use this script from the linked video(for want of any better ones?):-
Derived from this page:-

And :-

From the method shown in the video.

 version: "3.3"
     container_name: 'portainer'
     image: 'portainer/portainer-ce:latest'
       - "9000:9000"
       - "9443:9443"
       PUID: '1002'
       PGID: '100'
       TZ: 'Australia/Canberra'
       - './var/run/docker.sock:/var/run/docker.sock'
       - './srv/mergerfs/MergePOOL/appdata/portainer/portainer_data:/data'
     restart: 'always' 

I follow the instructions and use the “up” tab to upload/compose(?) the file and if it is all OK you get a Green “up” indication under the status column. I do get a brief green “up” but then it reverts to a red “down” status.

If I go to the “Containers” menu choice under the “compose” menu I can see there are no ports assigned / set and it all turns to custard there.

So any clues?

PS - I have tried playing with the port numbers and that makes no difference.

(I can use the install script in the CLI:-

docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v 
/var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

And that does work but I am being pedantic and need it to work with in OMV!)


Hi @Denys67462 - welcome to the forums :slight_smile:

We can certainly help with a lot on this forum but this might be one for the folks at OpenMediaVault.

in any case, you could:

  • Roll back OMV to a version that works the way you expected it to for this project
  • raise an issue with OMV. If versioning has created this problem then it may be an unintended side effect. Perhaps raise an issue so the developers can get this functionality back on track.

This sounds like it would be a better topic to raise on the OMV forums - its a pretty esoteric subject and I doubt the users on this forum have made it as far down the OMV rabbit hole as you have on this one. I know it sucks to be bounced around a bit when looking for help, but I’m sure you’ll want to take this one to the experts.