openmediavault-compose 6.7 Convert original docker-compose.yml file to "Files" Questions

In recreating the portainer container with the new system, if I'm understanding the Files section of the new Dashboard docker Compose system I could create individual yml files for the containers in my original docker-compose.yml file and manage my container updates. I attempted to do this, but the system does not appear to "link" an existing container to one of these new yml files in how the portainer entry I created will show the container status.

I assume this means I would need to do similarly for my existing containers as I did for portainer and remove the existing container and have the Dashboard system recreate it?
Is there a way to import my original docker-compose.yml file to create individual yml? I can do it manually, but figured I'd check if this has been "automated".
In doing this, I also assume if I wanted to update the container I would no longer be able to do so from the command line?

Thanks for the help/answers!

Ok, so it sounds like the answer is:

Yes, and the containers need to be redeployed via the Dashboard from now on to have the containers properly manageable by the dashboard, and the yml information must be manually entered.

Quote from ryecoaaron

The plugin would have to try to use portainer's compose file and environment files in order to manage the containers. And I'm not sure portainer would like that.

I did write a script to *try* to import compose files from portainer. I don't use portainer so it hasn't had a lot of testing. But worst thing you would have to do is delete something that imported wrong.

You can run docker compose commands from the command line against files in the plugin but you need to know the paths/names for the compose file and environment file(s). You cannot edit the files though. The OMV database is the source of truth. See this post for other info - RE: Old compose files after OMV restore

Understood! Easy enough for me to manually recreate, I wanted to make sure I wasn't missing something. So far the OMV Dashboard has worked well and adding container files is easy, so I'm on board with doing the work through it.

Thanks for all the work on this, it's a nice addition to the Dashboard.

Ah, ran into something.

My Nextcloud container has,

    depends_on:
      - mariadb

However even with mariadb container installed I get an error with the Nextcloud container.

Is this not supported?

Should I have both containers in the same File, or is there something else I need to be doing?

thanks!

update: I created a File with Nextcloud, mariadb, and swag, and created it that way. This puts them all in the same stack together, not sure if that is why it wasn't working before?

Understood!

In the past I was able to update one of the containers on it's own. With them being part of the same File, is there a way to do this from the Dashboard interface?

thanks!

Quote from ryecoaaron

Each "service" or container in the compose file will have a separate line on the Services tab. You can click Pull then Up to update each one individually.

Ah, the Services tab! perfect, thanks!