omv-extras 6.3 / openmediavault-compose 6.7

I think the updated screenshot is the help I needed.

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 '/Docker_Config/openmediavault-compose//Portainer/Portainer.yml' --env-file '/Docker_Config/openmediavault-compose//Portainer/Portainer.env' up -d 2>&1': The Compose file '/Docker_Config/openmediavault-compose//Portainer/Portainer.yml' is invalid because:
volumes.portainer-data value Additional properties are not allowed ('name' was unexpected)

Same here. is there way of moving the data from that volume to a regular folder and ensuring Portainer uses it?

Currently it's pulling in its stacks as "created outside Portainer"

Simply removing the line results in:

Volume portainer-data declared as external, but could not be found. Please create the volume manually using `docker volume create --name=portainer-data` and try again.

docker volume ls shows:

local portainer_data

I'm guessing this is an underscore typo?

Zitat von stinkycheese

Duly noted - thanks for taking the time to reply.

Here's exactly what I did:

1. ssh'd: docker container stop portainer
2. ssh'd: docker container rm portainer
3. Clicked "add example" on the Files tab of the compose plugin, hoping to select the portainer-omvextras example, as instructed - but there no items in the drop-down list.
4. Refreshed browser cache, tried a different browser, rebooted everything, lit a candle - still couldn't see any Examples in that drop-down list.
5. Restored OMV from a recent backup & all working as it did prior to update.
6. Updated OMV-extras again with a somewhat better result - I can now see the examples and select one.
7. Unfortunately, I now get stuck at a persistent error objecting to something in the recommended example's YAML:
   
   "volumes.portainer-data value Additional properties are not allowed ('name' was unexpected
   
   I have no idea how to get past this, but I'm sure I will.

Zitat von chente

This is so in that document because the proposed procedure is to install the docker folder on a separate drive from the operating system. The reasons are explained in the document a little earlier.

If you want to keep the default path /var/lib/docker you don't need to reinstall docker.

It all depends on what you want to configure and how you want to do it.

Yes...that's why I was letting Vitaman know how to set the Docker folder.

That user asked how to set the Docker folder as directed in OMV Docker guide.

( RE: omv-extras 6.3 / openmediavault-compose 6.7 )

As you recall, we used to do that before installing the OMV-compose plugin to ensure Docker would use the specified folder.

Now we do it after installing the plugin...but before actually installing Docker.

Of course, the new instructions show that screenshot and the steps to do this, but I didn't want to just RTFM my response.

You guys are pretty patient. Appreciate it.

Zitat von chente

If the only problem is that the examples do not appear, copy the content below in a new File and implement it, the result will be the same.

Code

---
version: "3"
services:
  portainer:
    image: portainer/portainer-ce:latest
    container_name: portainer
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - portainer-data:/data
    ports:
      - 9000:9000
volumes:
  portainer-data:
    external: true
    name: portainer_data

Alles anzeigen

And yet it continues to object every time:

Portainer.yml is invalid because:

volumes.portainer-data value Additional properties are not allowed ('name' was unexpected)

I understand this compose plugin change is in fact very simple and works 100% of the time, but until it's even simpler and works more than 100% of the time, I'm rolling back to 48 hours ago & going to steer clear of this update until the dragons have cleared out,

Zitat von KM0201

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)

Can other types of tasks like creating networks, removing images, etc., can be done by Portainer? if I remove a container through Portainer will the change happen in the plugin as well or will the non-existent container continue to appear? Does the plugin have options to do this sort of thing and also start and stop a container?

Here's what appears to be the correct, working example:

---
version: "3"
services:
  portainer:
    image: portainer/portainer-ce:latest
    container_name: portainer
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - portainer_data:/data
    ports:
      - 9000:9000
volumes:
  portainer_data:
    external: true

Zitat von KM0201

docker stop container_name

Jep, that's what I did in the meantime...

Zitat von KM0201

Is there a reason you need them all in one stack/compose file? Having them separate, also makes them easier to update, as you don't have to redeploy the entire compose file, just to update one container.

... but as it is sometimes just nice to use the GUI I will split the stacks now and have everything within one tab.

Zitat von ryecoaaron

You are going to be waiting a long time then. There are no dragons and this isn't a compose plugin problem. This is a "docker-compose complaining about the your portainer volume" issue. I would guess you still have portainer running. If you insist on continuing to use portainer, I would recommend you exporting your portainer data, removing the portainer container and volume, then create a new portainer compose in the compose plugin, and import your data.

The gulf between my level of knowledge and your own makes me appreciate your incredible dedication & commitment to everything OMV - thanks!

neil

Zitat von topi

So how did you do it without the yaml files to get all your configs back for each of your Docker applications? Or did you start from scratch?

I solved it getting back all the application configurations. I try to summarize what I recommend to do in these cases:

1- get a yaml file with autocompose with the command docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose name_of_your_container

2- stop the container with docker container stop name_of_your_container

3- with a text editor change the name of the container contained in the yaml file, something like "container_name: name_of_your_container" becomes "container_name: name_of_your_container-new" (by changing the name of the new container we can keep the old one until everything is went right)

4- in OMV Compose/File/Create name the new container "name_of_your_container-new" and paste the contents of the new yaml into window 1 (File), ignoring window 2 (Environment)

5- at this point you need to save and then select the cointainer and give the Up command (up arrow)

6- during this procedure there will be some errors, by reading them carefully you should understand where to put your hands to fix the file we have pasted. Select in Files "name_of_your_container-new" and click on Edit. Here we can make the changes. Generally it is about removing some parts that are not needed, I list some examples:

removed:

networks:
- bridge

removed:

networks:
- hosts

removed:

command:
- 'dumb-init /etc/openvpn/start.sh'

modified:

devices:
- CgroupPermissions: rwm
PathInContainer: /dev/dri
PathOnHost: /dev/dri

in

devices:
- /dev/dri:/dev/dri

7- once the errors have been resolved, the new container will start perfectly keeping all the settings it had previously, and at this point you can delete the old container with docker container rm name_of_your_container

Zitat von ryecoaaron

compose 6.7.5 is in the repo now and adds a hyperlink to each tcp port (should skip udp). The hyperlink works just like the kvm plugin - it gets the fqdn of the host from the OMV database. Seems to work better than portainer that on my system is just doing something like this - 0.0.0.0:28080 (which doesn't work).

Amazing, nice and quick!

Thank you so much