HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
docker
compose
Go2014–2026
docker / compose

compose

Define and run multi-container applications with Docker

44Distinct people
49Mentions
0Explicit recommenders
38.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Define and run multi-container applications with Docker

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

  • moby/moby · linked in 3 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year49 dated mentions

Observed mentions: 2014-02-28 16:34:58 UTC to 2026-02-25 14:53:38 UTC.

0510152014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC321
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC14311
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC413
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC514
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC523
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

14 sources
NB: I'm one of the founders of the Kubernetes project I'd recommend anyone trying to install Kubernetes check out: https://get.k8s.io/ Or the single node Docker based instructions: https://github.com/kubernetes/kubernetes/blob/master/docs/ge... Or boot2k8s: https://github.com/skippbox/boot2k8s Or kubernetes on OS X: https://github.com/rimusz/coreos-osx-gui-kubernetes-cluster Or of course the "as a service" versions like Google Container Engine, CoreOS Tectonic, etc. We're definitely also working on simplifying the install instructions. I'd also like to expand a little on some of the features that differentiate Swarm from Kuberentes, namely: * Secrets * Replicated sets of containers * Rolling update from one version of code to the next * AutoScaling (Kubernetes 1.1, in Release Candidate now) * HTTP load balancing for autosc
Read the rest
aling * Load balancing for sets of objects (e.g. Frontend) * Service discovery of those replicated sets (Swarm has discovery for individual containers, but no concept of Service) In general, our goal is to build a system that makes distributed system construction easier. I would also refer people to the discussion in https://github.com/docker/compose/issues/1899#issuecomment-1... as well as https://github.com/docker/docker/pull/8859 on why we feel that the Node-based Docker API is problematic for a cluster level API.
In Docker Clustering Tools Compared: Kubernetes vs. Docker Swarm
I started looking at Docker during vacation last week. I had a slightly outdated copy of Boot2Docker that didn't play well with VirtualBox 5.0. With limited bandwidth, I downloaded the docker-machine executable rather than the whole Boot2Docker package. Worked fine, and I was able to set up a variety of containers. When I got back to work this week, I started setting some of this up on my work Mac, and found a release candidate for the Docker Toolbox. It looks like it's the docker, docker-machine, and docker-compose executables plus the Kitematic GUI (haven't tried that yet). Looks like a decent package. Grumpy, off-topic digression after a week with limited Internet: please supply offline docs (Unreal), don't put a git clone command in the configure script to build them (Rust), don't require an external crate in a tutorial (random n
Read the rest
umber generator for Rust), don't put a link to a CDN in your offline docs (Leap Motion SDK), don't require activation after a 2 GB download (Unity Personal). I did luck out and find a WebSocket library in the Go tutorial, which I used to grab JSON from the Leap to load into MongoDB (in a Docker container). Grumpy, mostly on-topic digression: docker-compose doesn't work on my work Mac, and no one seems to know how to fix it: https://github.com/docker/compose/issues/271 Haven't yet managed to rebuild it locally as suggested. Edit: some observations after installing Docker Toolbox. Kitematic is an Electron app (complete with a Toggle DevTools menu that covers the window with a web dev console). It doesn't tell you what it's doing, but docker-machine shows that it created a machine named default using the VirtualBox driver with the default settings. Opening the Docker Quickstart Terminal stopped (and deleted?) the machine that Kitematic made and started a new one with the same name and settings. I think I'd be just as happy with only the docker and docker-machine executables.
In Docker 1.8 released
Docker is a cute little tool that gives people who aren't that great at Linux the illusion that they know what they're doing. Throw in the use of some "Container" semantics and people become convinced it's that easy (and secure) to abstract away the containers from the kernel. But it's not, at least in my experience; not to mention that as of now, anything running Docker in production (probably a bad idea) is wide open to the OpenSSL security flaw in versions of 1.0.1 and 1.0.2, despite the knowledge of this issue being out there for at least a few days. Docker's currently "open" issue on github: https://github.com/docker/compose/issues/1601 Other references: https://mta.openssl.org/pipermail/openssl-announce/2015-July... http://blog.valbonne-consulting.com/2015/04/14/as-a-goat-im-...
In Ask HN: What is the actual purpose of Docker?
Besides just actually running software, I also find it really neat when projects use docker to build their entire application. It provides an effective means of documenting all of your dependencies and making reproducible builds. Take the docker-compose for example. You can just check the code out, run a single script that builds the project for your environment and everything is pretty much self contained in the dockerfile (https://github.com/docker/compose/blob/master/Dockerfile). You don't have to clog up your host computer with deps and you get an executable plopped into an output bin folder. Additionally, the steps in the dockerfile get cached so subsequent builds are really fast.
In Ask HN: Why use Docker and what are the business cases for using it?
Oh cool, another change to fig/docker-compose that doesn't include the most requested feature: https://github.com/docker/compose/issues/495 As the person who wrote the PR for its solution and have been waiting for it to get merged for months, this is super, super frustrating. If you guys don't want to put the logic in, reject the PR and close the issue as won't fix. Quit stringing the community along.
In Docker 1.6: Engine and Orchestration Updates, Registry 2.0, and Windows Client
I've got a bone to pick with the new Docker Compose. Take a look at this issue: https://github.com/docker/compose/issues/495 Back in January I went through the effort of outlining a solution that was approved by the maintainers before implementing it. After I provided a PR, I responded to revision requests by the maintainers, and still haven't seen this change go into the project. It's a simple change. If this feature isn't the architectural direction Docker wants, they need to close the issue and reject the pull request, instead of changing the project over and over again so that I have to maintain a PR that's over three months old. Very uncool.
In Docker 1.6: Engine and Orchestration Updates, Registry 2.0, and Windows Client
I started with Don Libes' classic book on Tcl/Expect[1] and am moving on to the 3rd edition of Clif Flynt's book[2]. Someone in #tcl on Freenode suggested that this set of essays would be a good resource for exploring some of the new/er features in Tcl. I'm experimenting with using Tcl as a basis for rapid prototyping and testing[4] of services and service compositions built with docker and docker-compose[5]. It would be awesome if O'Reilly would consider making Exploring Expect[1] an Open Book[3] – it's an "oldie but goodie"! [1] http://shop.oreilly.com/product/9781565920903.do [2] http://shop.oreilly.com/product/9780123847171.do [3] http://www.oreilly.com/openbook/ [4] http://caiusproject.com/ [5] https://github.com/docker/compose
In Topics in Tcl Programming

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.