Reverse engineer compose files from existing resources

[meyayl]

Is your feature request related to a problem? Please describe

Whenever a compose project or swarm stack is deployed with another client, Portainer is not able to manage the compose project/swarm stack.

Describe the solution you'd like

Please add a feature to generate a compose file from deployed resources.

Every resource of a compose project or swarm stack has a label that allows to identify which resources belong to the compose file. Thus, we can identify which containers, networks, volumes, and in case of swarm secrets and configs belong to the resulting compose file.

To reduce the number of elements in the resulting compose file to those that are actually specified, we could:

• generally:
  • remove every element for a resource in the compose file where the current value matches the default value docker uses while creating the resource
• for containers:
  • Additionally remove every element where the value matches the values from the image.
  • make use of labels to identify the service name to be used in the compose file
• for networks/volumes:
  • make use of project/stack names to identify the resource name in the compose file
  • if the resource name is not prefixed with the project/stack name, set a static resource name

And probably some other tweaks I didn't think of yet.

Note: it would also make sense for standalone containers (=not belonging to a compose project/swarm stack) to apply the logic for containers from above when updating containers to newer images.

Describe alternatives you've considered

Use autocompose instead and paste the resulting compose file into Portainer.

Additional context

No response