libswarm demo – logging

At Dockercon, we announced a new project being worked on called “libswarm”. I wanted to clarify what exactly libswarm is, what it does, and what it doesn’t do. First, libswarm is not itself an orchestration tool. It does not and will not replace any orchestration tools. Libswarm is a library first and foremost and not an end-user tool. It is a library that helps make it relatively trivial to compose other disparate tools together, including but not limited to orchestration tools. Just a quick demo showing off what libswarm can do with logging. I will be using code from this gist: https://gist.github.com/cpuguy83/b7c0f42e903bc13c46d6 Demo time! # start a container that prints to stdout docker -H tcp://10.0.0.2:2375 run -d –entrypoint /bin/sh debian:jessie -c \ ‘while true; do echo this is a log message; sleep 1; done’ # fire up swarmd ./swarmd ‘logforwarder tcp://10.0.0.2:2375’ stdoutlogger Getting logs Continue reading…

Scott Johnston

Continued Community Momentum Around Orchestration

One of the great aspects of the Docker community is its ever-growing ecosystem of tools, technologies, and services built on the Docker platform. Today, we’re excited to join with Google to highlight the momentum of their Docker orchestration and workload scheduling tool, Kubernetes.  Based on tools Google uses internally to run large workloads like Gmail and Search, Kubernetes was first announced at last month’s DockerCon, the Docker community’s inaugural conference. Orchestration is an important category of tooling for distributed applications built on the Docker platform, and Kubernetes joins Mesos, Consul, Fleet, Geard, ZooKeeper, and others, each addressing a particular use case or niche. In Kubernetes’ case, it coordinates Docker workloads so as to take advantage of Google Compute’s underlying operations and infrastructure. Given Google’s expertise in large scale operations, Kubernetes is a welcome addition to this tool category. This proliferation Continue reading…