I was running portainer via docker-compose.
You say you were running Portainer via docker-compose, so the procedure should be applicable for retrieving containers and deploying them to the openmediavautl-compose GUI.
I do every config through docker-compose on cli.
You didn't say that in your first post. If you implement the containers directly in the CLI, what is the problem then? The plugin isn't going to help you much with containers run from the CLI.I also don't understand why you use Portainer if you run the containers from the CLI.
So mainly i used CLI for docker compose, the only thing i asked was if there was a motive for all the sudden after the update all containers were deleted. Since i never used OMV to managed docker. That was it.
The update does NOT delete any containers. If you installed and manage them in the CLI they should continue to work exactly the same as before.
Why do you say they have been deleted? That's impossible without doing anything but updating.
The update does NOT delete any containers. If you installed and manage them in the CLI they should continue to work exactly the same as before.
Why do you say they have been deleted? That's impossible without doing anything but updating.
Right, so i am just stating what happened after the update. I could see docker was running, though all images and networks where deleted. Like i said, was easy to sort out (just deployed them all again). I was just looking for an explanation since never happened before while running OMV.
Like i said, just curious since it was literally after yesterday update.
So mainly i used CLI for docker compose, the only thing i asked was if there was a motive for all the sudden after the update all containers were deleted. Since i never used OMV to managed docker. That was it.
It should not have deleted your contianers... Something else went haywire... All the plugin did was change how docker could be managed within the webUI
Right, so i am just stating what happened after the update. I could see docker was running, though all images and networks where deleted. Like i said, was easy to sort out (just deployed them all again). I was just looking for an explanation since never happened before while running OMV.
Like i said, just curious since it was literally after yesterday update.
Did you try restarting docker? It almost sounds like docker started before your drives with docker data mounted.
Try restarting docker (systemctl restart docker) and see if that brings things back to normal.
Right, so i am just stating what happened after the update. I could see docker was running, though all images and networks where deleted. Like i said, was easy to sort out (just deployed them all again). I was just looking for an explanation since never happened before while running OMV.
Like i said, just curious since it was literally after yesterday update.
Since I haven't tested that, I'm not sure what to say, since all my containers run in docker-compose via the plugin. But I suppose that the only thing that could have been is that they were detained, nothing more.
I also don't see how the update would remove networks or images, that's not possible.
I did all my containers via plugin, and I've just checked via ssh and using docker ps, all my containers list ok. You said docker was running, did you set the docker folder somewhere else?
Don’t have an account yet? Register yourself now and be a part of our community!
