James Carppe

For Portainer to work across a Swarm cluster, even when deploying containers to specific swarm nodes, the agent needs to be running on all the nodes in the cluster. Without...

This generally happens when an updated version of that image and tag is pulled, and Docker untags the old version of the image. We are looking at what we can...

Thanks for this - this is something that we're aware of and have an internal issue open around, so I've added your feedback to this. The reason this happens is...

This is with our engineering team who are looking at fixing it in a future release. I don't have an ETA for it at this stage sorry.

I believe this fix is flagged for 2.17. There look to have been some code conflicts that meant it didn't quite make it into 2.16 unfortunately.

Portainer doesn't currently support using relative paths in compose files, but more importantly doesn't fully support building images as part of a stack file. The reason this doesn't work right...

Thanks for the feedback! This is something we're aware of already, and we're looking at refining in an upcoming release.

Can you share the stack file you're using? I wonder if there's special characters or some formatting weirdness that's causing this to fail in 2.15.

I haven't been able to replicate this behavior locally at all. I've used a basic WordPress stack to test - you can see it in [this repo](https://github.com/jamescarppe/wordpress-stack) - which includes...

> To confirm how I can do a completely fresh install of portainer. Can I simply dump all of my persistent data outside of the /compose/ dir (which I believe...