-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose #39
Comments
What would you use that for? The purpose of this script as I originally envisioned it is to let you run ad-hoc containers that were launched with lots of switches. What's the use-case that you have in mind for adding support for docker-compose output format? |
Generating docker-compose.yml is useful for taking snapshots of a running set of containers. It would be a useful dev-ops tool. |
It would be an interesting challenge to try to implement this. docker-compose is so much more than just containers, though. It's networks, volumes, etc. practically the entire docker engine API would have to be employed. |
This is the exact use case I've found myself with today. I have a host running 39ish containers that were created using a mix of compose, run commands, and portainer, that all need to be recreated on a different host while I rebuild the first one. |
you can pipe the output of unfortunately that codebase is npm and this one is python or else we could have ourselves a pr with the combined functionality pretty quick. either way, using these tools together is a great way to jump from ad-hoc to managed... now we just need the same for kubernetes (jk) |
Have you thought about generating a docker-compose file as well? While they typically combine a few services, a fragment would work well.
The text was updated successfully, but these errors were encountered: