Kitematic: docker-compose support in Kitematic UI

[saulshanabrook]

Is it possible for kitematic to provide support for docker-compose?

[andyshinn]

This would be awesome to help bootstrap non-devs in to testing environments in Docker. I'm thinking of scenarios around customer service and QA. Specifically where the ops team can provide Kitematic and a repository for them to build and run the entire application (not just one container) similar to how developers just do fig up today.

[gorghoa]

I do agree, especially now that docker-compose is fully supported by docker ;)

[saulshanabrook]

Is there any interest in moving this issue onto the roadmap?

[rweald]

:+1:

[nickblt]

:+1:

[g12n]

Yes Please. Maybe add a visual Interface to compose and connect the containers.

[metra]

:+1:

[DieterReuter]

:+1:

[dtornow]

+1

[mainiak]

:+1: (bundled with Kitematic - as docker-machine and others - should be enough for me, UI support would be nice)

[JanJakes]

:+1:

[Globegitter]

:+1:

[karellm]

:+1:

[bmbroom]

:+1:

[IanVS]

:+1:

[pnegahdar]

:+1:

[bruienne]

:thumbsup:

[miguelpuyol]

[emilkje]

:thumbsup:

[jacksoncage]

:+1:

[offlinehacker]

:+1:

[fabarea]

:+1:

[ludekslevercz]

:+1:

[droidment]

[GerDner]

:+1:

[djsly]

:+1:

As a starting point it would be great that kinematic pulls in latest stable release of docker-compose / swarm to have them available at the console

[alfonsfoubert]

:+1:

[florentb]

:+1:

[naneau]

Our development stack uses docker-compose, and it would be nice for our less CLI/Docker-savvy developers and QA people to be able to use Kitematic to manage it. Big :+1:

[funkytaco]

:+1:

[yingbo]

:+1:

[paulstanyer]

:+1:

[sheats]

:+1:

[zdexter]

:+1:

[tillsanders]

:+1: come on :heart:

[joostfarla]

:+1:

[StalkingKillah]

:+1:

[RSSGergelyMunkacsy]

:+1:

[DougThwaites]

:+1:

[szubtsovskiy]

:+1:

[thecb4]

[fsimmend]

:+1:

[leolara]

[syrusakbary]

:+1:

[christopherlakey]

:+1:

[preflightsiren]

:+1:

[kusmierz]

:+1:

[telemakhos]

:thumbsup:

[leolara]

I think it is clear how damaging for the application usage would be to implement this feature so disliked by everyone.

[kusmierz]

@leolara could you explain?

[leolara]

@kusmierz I was ironically expressing the overwhelming support of this feature request.
To be clear, what I literally was trying to say is:

"The support for this feature request is overwhelming and its inclusion would increase the user base"

[offlinehacker]

To give more constructive tip, than just liking this pull request, someone
could just probably integrate lorry.io from centruylink labs, which is
bacisally a docker compose file editor:
https://github.com/CenturyLinkLabs/lorry-ui and this blog post
http://www.centurylinklabs.com/lorry-io-pathway-to-docker-composable-apps/

On Sun, Jun 7, 2015 at 9:55 PM Leo Lara [email protected] wrote:

@kusmierz https://github.com/kusmierz I was ironically expressing the
overwhelming support of this feature request.
To be clear, what I literally was trying to say is:

"The support for this feature request is overwhelming and its inclusion
would increase the user base"

—
Reply to this email directly or view it on GitHub
https://github.com/kitematic/kitematic/issues/137#issuecomment-109793303
.

[christopherlakey]

I would be happy if Kitematic simply included docker-compose in it's command line distribution.

The current install overwrites the brew installed version of docker and doesn't include the docker-compose executable. Perhaps there is a separate ticket about playing nice with brew docker.

[ArondeParon]

:+1:

[chewmanfoo]

docker-compose in kitematic would be sweeeeeet

[roelvanduijnhoven]

:+1:

[aaronlks]

:+1:

[pbearne]

+1

[afoucret]

:+1:

[buremba]

:+1:

[estahn]

:+1:

[englandrp]

:+1:

[theoplatt]

+1

[halit]

+1

[ybouhjira]

:+1:

[jjasonclark]

:+1: times :100:

[jasonreich]

:+1:

[tomluczak]

:+1:

[NoiSek]

:+1:

[eristoddle]

:+1:

[mgenereu]

:+1:

[ghost]

:+1:

[ybouhjira]

:+1:

[cansik]

:+1:

[maechler]

:+1:

[yvoswillens]

:+1:

[benlangfeld]

I'm pretty sure none of these thumbs-up are going to make an ounce of difference in the world other than to annoy those who get email notifications. Perhaps you guys could all hit the Subscribe button instead? It's up there at the top right of the page.

[mchiang0610]

Docker compose is now included with Docker Toolbox, and you can use docker compose through the CLI button inside Kitematic.

Compose is not available on Windows yet, and when it does we will support it on Windows as well.

Thanks!

[tillsanders]

This is great news! However, I think people were really looking forward to an integration into the gui.

[leolara]

Vote here then: https://github.com/kitematic/kitematic/issues/1034 - docker-composer support in UI
@tillsanders @yvoswillens @maechler @cansik @ybouhjira @lucasmorano @mgenereu

[mchiang0610]

@tillsanders @leolara Thanks, I'll just reopen this issue here and close the other one. Let's continue the discussion here.

[mchiang0610]

@leolara @tillsanders @yvoswillens @maechler @cansik @ybouhjira @lucasmorano @mgenereu

Can we brainstorm what you'd like to see in the UI for compose support? I have my assumptions but want to hear it directly from our users.

[iBobik]

I think composer yml should be there in same way like pulled img - in the
sidebar is entry for it and you can just start it or stop.

Can you imagine it? Or should I make some sketch?

Jan Pobořil

2015-09-12 15:01 GMT-05:00 Michael Chiang [email protected]:

@leolara https://github.com/leolara @tillsanders
https://github.com/tillsanders @yvoswillens
https://github.com/yvoswillens @maechler https://github.com/maechler
@cansik https://github.com/cansik @ybouhjira
https://github.com/ybouhjira @lucasmorano
https://github.com/lucasmorano @mgenereu https://github.com/mgenereu

Can we brainstorm what you'd like to see in the UI for compose support? I
have my assumptions but want to hear it directly from our users.

—
Reply to this email directly or view it on GitHub
https://github.com/kitematic/kitematic/issues/137#issuecomment-139815435
.

[djsly]

That would be a good first step.

Allowing us to start / stop/ restart / rm a stack of containers using a pre defined docker-compose.yml file.

A second step could be to dynamically create a docker-compose.yml from the UI. Drag and dropping existing images or images from the docker hub. Linking them visual et edition their volume / portion the fly

Finally we could save and export our topology to docker- compose.yml or even Visio / JPEG / PDF.

On Sep 12, 2015, at 7:47 PM, Jan Pobořil [email protected] wrote:

I think composer yml should be there in same way like pulled img - in the
sidebar is entry for it and you can just start it or stop.

Can you imagine it? Or should I make some sketch?

Jan Pobořil

2015-09-12 15:01 GMT-05:00 Michael Chiang [email protected]:

@leolara https://github.com/leolara @tillsanders
https://github.com/tillsanders @yvoswillens
https://github.com/yvoswillens @maechler https://github.com/maechler
@cansik https://github.com/cansik @ybouhjira
https://github.com/ybouhjira @lucasmorano
https://github.com/lucasmorano @mgenereu https://github.com/mgenereu

Can we brainstorm what you'd like to see in the UI for compose support? I
have my assumptions but want to hear it directly from our users.

—
Reply to this email directly or view it on GitHub
https://github.com/kitematic/kitematic/issues/137#issuecomment-139815435
.

—
Reply to this email directly or view it on GitHub.

[dkapanidis]

Here is cool idea for kitematic + docker-compose integration:

Give the possibility to add "Launch with Kitematic" button on Git/GitHub repositories that resolves to kitematic://up/https://url/to/docker-compose.yml which in turn launches the stack. See GitHub Desktop as an example of such integration.

[thaJeztah]

Similar issue in Docker Compose; https://github.com/docker/compose/issues/1215

@spiddy also see https://github.com/docker/compose/issues/1818#issuecomment-129081511, https://github.com/docker/hub-feedback/issues/57, https://github.com/docker/compose/issues/1597

[psychemedia]

@mchiang0610 I'd quite like a couple of compose features:

• a selection of "composition" icons that relate to compose files rather than docker images, from which I can launch a particular composition;
• a composition editor, in which I can drag container images onto a canvas and then wire them together to create a skeleton for a compose file that can then be filled in with other properties (ideally, graphically).

[dekz]

I'd like to see a import from docker-compose.yml option.

[FrenchBen]

So I have this PR that's gone stale: https://github.com/kitematic/kitematic/pull/898
Should I bring it back up to date since we've now got docker-compose inside the docker toolbox?

[bacheson]

+1 how is this not supported at this point?

[leolara]

:+1:

[mgenereu]

Don't use Kitematic, use Mindcraft.
http://blog.docker.com/2015/11/dockercraft/

[leolara]

I am thinking about it

[v1nc3ntlaw]

:+1:

[leolara]

This Sunday the issue will have its first birthday!!

:birthday:

:+1:

[lianguan]

:+1:

[jruef]

:+1:

[stkiss]

:+1:

[MPJHorner]

:+1:

[ghost]

:+1:

[ronanguilloux]

:+1:

[kristianpaul]

:+1:

[defeated]

:muscle: :grin: :+1:

Revisiting Kitematic this weekend in hopes to give our design team an easy way to launch our web app. An ideal workflow would (for my use case) would look something like:

1. open Kitematic
2. File | Import | browse to docker-compose.yml
3. Select any volumes to map on their local drive
4. Run!

[jtraulle]

:+1:

[gastounage]

:+1:

[vladynet]

:+1:

[samnydahl]

:+1:

[andyfleming]

:+1:

[eduwass]

👍

[sergeibershadsky]

:+1:

[etweb37]

+1

[riteshnaik]

+1

[cedricve]

+1

[tranvietanh1991]

+1

[rhangelxs]

+1

[lamjo]

+1

[sebastian-alfers]

+1

[jackiig]

:+1:

[chrowe]

This is what I am thinking...

Getting the compose file

1. Import local file
2. Search remote database. e.g. https://github.com/docker/compose/issues/1597

Using

1. List with containers on the left and show related containers as sub items that could be expanded and collapsed.
2. Map all the same basic compose commands that already have UI elements. Start, Stop, Restart. View Logs. Delete. Port bindings?

[frdmn]

👍

[mainiak]

I know it would beneficial just to support 'raw/native' docker-compose in Kitematic,
but Rancher already has their own compose support so ... integration with Rancher itself I consider neat and just by using Rancher API it might solve compose requirement as well.

I'm sure that should be another issue/ticket for Rancher API support as feature request and maybe another one to docker-machine, maybe?

[mercuriete]

:+1:

Something like
option 1:
open file docker-compose.yml
then cd folder && docker-compose up -d

option 2:
paste to input text
only compose this text without building support, only download images for quickcly setting up stacks.

option 3:
paste URL of recipe (docker-compose.yml URL)
curl URL | docker-compose or something like this.

[mindesik]

docker-compse.yml file picker feature will be nice 👍

[prateek05]

👍

[bmwillrath]

👍 Sorry to be another thumbs up notification.
Learning the world of docker is so much easier with a GUI, Kitematic has been awesome so far, but now I'm at a roadblock cause I can't play with docker-compose without diving into CLI.
CLI doesn't scare me, but it sure frustrates the fuck out of me sometimes, I just need something pretty, it helps me learn.
Please add this. Kitematic needs it, and so do the 91 people I counted above.

[Badisi]

👍

[fortis]

👍

[ndubbaka]

👍

[FrenchBen]

👍

[SoerenHenning]

:+1:

[janhartigan]

Probably don't need to keep commenting with thumbs up, guys. GitHub has the reaction feature now.

[Gekctek]

+1

[nicbarker]

+1

[gladiatorAsh]

I am sorry to be posting another thumbs up but need to reiterate that it would be great if we had docker compose feature from the UI itself. Pretty please :heart_eyes:

:thumbsup: :100: times

[AlexandrePieroux]

👍

[leolara]

👍 💯 times

[FrenchBen]

Obviously everyone here wants this - I need feedback on how this should work/behave.
How do I open the file? Can I edit the file once it's been opened? Is there a location where my compose file live? Does it group the containers? If yes, how?

There's a lot involved with the simple 'open docker-compose file' and I need some help to figure out how it should work.
Please Open a new issue with Proposal: Docker-Compose in the title and provide detailed behavior for all cases and also behavior.
If you can provide screenshots, that's even better!

Keep in mind that compose files can provide different output (aggregated) and also can error out with compose-specific issues.

Thanks for the help everyone!

[janhartigan]

@FrenchBen my initial thoughts:

1. There should at the outset be a way to docker-compose up any particular compose yaml file.
2. When any up is run, it should group all containers started by it. There should be a way to quickly view the running logs and current status of each container. This should probably include things like opened ports, volume mappings, and anything else that is relevant that can be defined in the docker compose yaml.
3. There should be a way of running down on the entire group of containers, just like you would run docker-compose down from the yaml's directory.

Those are just top-level things I would see as a requirement. When I'm developing a compose file and related docker files, I primarily use the specific container logs and jump into container-specific bash. I couldn't immediately think of a great way to standardize "jump into the bash" since (I think) there's nothing stopping a container from not having a bash. Maybe mapping custom buttons that let you run a docker command on a specific running container?

[psychemedia]

My current workflow for starting up compositions is to use the Kitematic command line to open a tab in a new (Mac) terminal tab where the current tab in the uppermost terminal window is set to the directory containing my YAML file. Then I can simply run a docker-compose up -d/start. Once running, the various containers associated with that compose file are then listed separately in the Kitematic left-hand sidebar.

@FrenchBen, here's a straw man based on that...

At a basic level, this could be replicated by a File->Compose->Run menu option to open a wizard that lets me select a directory (possibly offering recent paths in a drop down), checks that it contains a docker-compose.yml file, and offers me Up/Start/Stop/Down buttons with appropriate switches as check boxes.

The Up and maybe Start option I can imagine using, but not the Stop/Down.

The next step might be to consider a "profile" for each of the paths to docker-compose files, associating a name with that composition (by default, based on the directory name containing the docker-compose.yml file). This gives us a composition instance to talk about.

As far as monitoring running compositions and stopping or restarting them, it would be nice to use the current left hand container sidebar.

To list the running containers, these could either be grouped in the sidebar (in which case, you also need a label somewhere for the composition instance as a whole that can be used to select the composition as such and display information about it), or use a single slot to list each instance of that compose profile along with support for opening a menu or accordion item.

Opening the menu item (either as an according dropping down, or a menu to the right and down) could display a list of the containers in the composition (letting you open info on a single container in the normal way). (This menu model could also work for grouping containers linked to a data volume?)

Currently, container controls have a delete button on each listed container in the left hand side bar. When a container is selected, container info appears in the main panel and start/restart controls etc along the top toolbar.

Selecting (rather than uncollapsing) a composition item in the left hand sidebar should offer up/start/stop/down controls along the top toolbar with some sort of support for switches and in the main panel show information relating to the composition as a whole.

Selecting a container listed under the composition selects info about it in the normal way.

To prevent actions on individual containers within a composition, constraints on allowable actions may need to be applied to containers listed under a particular composition.

To make it easier to re-use docker-compose files, the New/Docker hub listing panel could be split in two, the top half showing container images as per the current model, the lower half displaying links to recent docker-compose locations. Down the line, this might be extended to a composition repository (Panamax has this model, I think?) from which composition files could be selected, downloaded and run.

Down the line, support for creating compositions within Kitematic by selecting and wiring together containers from the Docker hub listing would be nice, maybe in a composition creation area presented as a split screen below the hub listing, allowing containers to be dragged from the hub listing into the composition area.

[DonRichards]

+1 Please make this happen.

[maltehuebner]

👍

[akhilputhiry]

would love to have this

[moeiscool]

+9000

[offlinehacker]

That's not even over 9000

On Sat, 20 May 2017, 01:58 Moe, [e-mail] wrote:

+9000

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/docker/kitematic/issues/137#issuecomment-302835661,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjvSw1J6XvhG8gXcleU4M1GxBtPW-wwks5r7iyygaJpZM4DICNl
.

[silverkorn]

👍

[josedacosta]

+1

[kopiro]

+1

[ghost]

👎 I like my Kitematic simple. When I need to grow I'll grow into Docker Cloud.

[ghost]

@psychemedia docker-compose up -d/start is not a valid CLI command. Are you sure that isn't a typo? Also, I ran the up sub with the -d flag from the TTY initiated by Kitematic and everything started just fine but I didn't see the containers appear in Kitematic as you described.

Some interesting thoughts though. Maybe _Stacks_ would be more appropriate since Compose v3 is made to support Docker Cloud and supports swarming, unlike v2 and AFAIK. But then again keeping things simple until until the tool comes out of beta would be the best approach to hit a 1.0. IDK.

[openStove]

+1

[psychemedia]

@jhabdas Apols: that was probably meant to read as something like docker-compose up -d or docker-compose up start.

As to containers appearing in Kitematic, I've noticed in recent versions sometimes they do, sometimes they don't... Not sure how much I trust Kitematic any more:-( Which is a shame, because I thought it held real promise as an app runner for users who won't go anywhere near the command line...

[ghost]

Thanks for the deets @psychemedia. I gotta admit I was scratching my head for a moment there. 😆 As for the tool I can only imagine it's extremely difficult to keep up with Docker. We've got a great base on something for the future. If the scope can be contained to something simple, and a 1.0 shipped, perhaps then it can keep pace with changes in Docker ecosystem and eventually allow more features over time. That's my .02 at least. Though your vision is indeed compelling.

[vladvarna]

+1

[wupmemo]

:+1: Yes that would be awesome.

[ghost]

FYI, some of you may find the following information useful if you're doing more than just toying around with Docker: GitHub Goes All in on Kubernetes - The New Stack

[zanderstrachan]

+1

[DonRichards]

So how many people have to follow this before it's implemented? Or is it even possible? Honestly just wondering.

[FrenchBen]

@DonRichards if someone wants to help implement this, it'd be great; that's really the hold-up.

[ghost]

@FrenchBen sorry for the meta. is it possible to add the help-wanted tag to this issue so that's clear for others?

[psychemedia]

Complementary to docker-compose support is being able to use Kitematic to build and seed a container from a Dockerfile + supporting files.

The original MyBinder project (now part of the Jupyter project as binderhub) would dynamically build an image from a github repo. The O'Reilly Launchbot does something similar on the desktop - but again, without support for docker-compose.

The reason I mention it here is that whilst the proposal for docker-compose support in Kitematic helps those of us wanting to use Kitematic to support use, by non-technical users, of linked Docker containers as part of a personal application workbench, we're still left with the problem of how to distribute things like a files as part of that workbench.

(An example use case might be a non-expert users who knows simple SQL and wants to be able to query across mixed JSON and CSV files from a Jupyter notebook UI using Apache Drill, but who doesn't want to have to worry about installing those applications and setting up the correct links between them. In addition, they may have data files and Jupyter notebooks they want to be able to share with other non-expert users using a similar workbench setup.)

So I'm now imagining the following scenarios:

• Kitematic as an application that can pull down pre-built images and launch them
• Kitematic as an application that could pull down pre-built images and launch them as part of a docker-compose composition
• Kitematic as an application that can build one or more images from a source repo (or config zipfile) and launch them as linked containers
• Kitematic as an application that can pull down a pre-built image and then copy in data files from a source repo or zipfile to a linked volume

[okor]

To help ease some of the pain points of working with docker, a coworker created a GUI to launch docker/compose things. Might be helpful to some folks. https://github.com/jplhomer/lifeboat

[MisterWang]

👍

[vsocrates]

Hi, has there been any progress on this? I'd love to get docker-compose supported for being able to easily allow non-developers to easily start using Docker. Thanks!