Whew! 22 pages... just to make certain I'm up to date.
Gotta admit I'd become pretty lazy with the updates... new update for OMV? Yeah... go ahead... who needs to read the release notes? Didn't even notice anything had changed at first - since the containers were all still running and I do most start/stop/update stuff either command-line or Portainer or through Home Assistant.
I like where this is going, though. So... thank you.
But I do have a reason for posting - though it's an odd one-off, I'm sure: I monitor my containers from Home Assistant and I stop/start them for various short-term usage. The way the integration works in Home Assistant goes well if a stopped container is "exited" but not "down" - as the button in Services, Compose, Files does. I can do an "stop" from command line or from Portainer (or from Home Assistant) and all works as expected. But the "down" button removes the container and breaks my monitoring and up/down control. Would be cool (for me at least) if the Services, Compose, Containers included a "stop" as well as "up" option. If not... no big deal since I have other ways to do it. But thought it might be worth mentioning that there is a meaningful reason for this function.
Again, much thanks and appreciation for the direction this is going. The Portainer / Yacht thing always seemed kludgy relative to other integrated functions and this seems really clean.
Oh, yeah... one other thing to share with anyone who reads this far:
Just to move forward but not lose my Portainer stuff (yet), I created all my containers in Services, Compose, Files but didn't kill them or remove them from Portainer (yet). Obviously, they can't be started in OMV until they're removed from Portainer... but it has the unexpected benefit of them all showing up in Services, Compose, Containers with all the accurate conditions of State / Status / Image / etc.
Potentially dangerous if one forgets why they wouldn't start this way... but seems like a nice reverse-integration option while transitioning.