I spent several hours on this last night and never got an answer that I felt was good enough to rely on.
I installed Portainer after setting up a couple of projects and the 'limited control' issue came up.
There doesn't seem to be any clear instructions about how to migrate from std docker-compose to Portainer managed stacks
People say 'remove and redo' but how about an example in your docs?
Let's say I have a basic Pi-hole installed using docker compose.yaml
How would we migrate this to Portainer?
Something like
copy existing compose.yaml
docker compose down
rm the container
rm the network
add volume to Portainer
add compose.yaml to Portainer
Run docker compose.yaml up
What are the downsides and upsides of doing this?
I note that Portainer creates it's own volumes - these aren't necessary for a project that was previously working, etc, etc...
I really just wanted to be able to edit .env files inside Dockge, but I figured it was worth taking another look at Portainer.
To put it bluntly, it's now sounding easier to use SSH to manage the .env files.
I spent several hours on this last night and never got an answer that I felt was good enough to rely on.
I installed Portainer after setting up a couple of projects and the 'limited control' issue came up.
There doesn't seem to be any clear instructions about how to migrate from std docker-compose to Portainer managed stacks
People say 'remove and redo' but how about an example in your docs?
Let's say I have a basic Pi-hole installed using docker compose.yaml
How would we migrate this to Portainer?
Something like
What are the downsides and upsides of doing this?
I note that Portainer creates it's own volumes - these aren't necessary for a project that was previously working, etc, etc...
I really just wanted to be able to edit .env files inside Dockge, but I figured it was worth taking another look at Portainer.
To put it bluntly, it's now sounding easier to use SSH to manage the .env files.