Aanand Prasad

Live Debugging with Docker

During the DockerCon 2016 keynote, I demonstrated a development workflow with Docker for Mac, going from a fresh laptop to a running app in no time. The especially cool part was when I live-debugged a Node.js app running inside a container from my IDE, despite having no Node.js runtime installed on my laptop. Here I’m going to show you how to do it yourself. Here’s what you’ll need: Docker: I recommend Docker for Mac or Windows, which are in public beta. An IDE which supports Node.js remote debugging: I used Visual Studio Code. A Node.js application: I’ll create a simple one as part of this tutorial.   Example Application Create a directory to work from: $ mkdir node-example $ cd node-example To get our app running, we’ll need 5 files: A JavaScript file to contain the actual app code A package.json Continue reading…

Chris Hines

Webinar Q&A: Docker Overview

Thanks everyone who joined us during our Docker Overview webinar. During this webinar, we gave a high level introduction to Docker, and let the audience see the platform in action during a live demo. The recording of the webinar is available to watch here or below. Featured presenter, Harish Jayakumar, Solutions Engineer at Docker, Inc., shares his answers to questions he received during the live presentation:    

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:// 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://’ stdoutlogger Getting logs Continue reading…

Victor Coisne

Global Hack Day Demo Videos

The biggest Docker event (so far)! This week was the first-of-its-kind Docker Global Hack Day! The growing number of Docker meetup groups around the globe has convinced us to organize an event that would bring the whole Docker community together despite the time difference. Such a global event would have never been possible without the engagement of every participants and the help of our meetup group co-organizers that managed to find places to host local editions of the Global Hack Day. With more than 400 participants worldwide (including the people registered for the remote edition) and 8 local editions, we are very thankful for such an awesomely active community. With such a great push from the community, we are confident that both Docker itself and upcoming Docker events will only get better and better. We have received numerous videos of Continue reading…

Get the Latest Docker News by Email

Docker Weekly is a newsletter with the latest content on Docker and the agenda for the upcoming weeks.

Victor Coisne

Docker Workshop at Geekdom San Francisco by Rackspace

  We had the pleasure to co-organize a Docker Workshop with Geekdom San Francisco (Rackspace) on Sept 12, 2013. It was truly amazing to see the number of people attending the first session of the workshop at 10:30am (picture here above).

Docker at DjangoCon US 2013

I had the pleasure of being chosen as a speaker at this years DjangoCon US conference in Chicago last week. My talk was mostly about Docker, but also how you can use it to make your life easier when developing Django. I think the talk went well, but due to the short talk time, I wasn’t able to go into too much of the details around how it relates to Django. I was also the first talk of the conference so I was the guinee pig for some of the technical issues, and my demo didn’t go as well as I had hoped. To make up for these two shortfalls, I felt I owed it to everyone who attended to write up a follow up blog post that included a more detailed demo covering the areas that I wasn’t able Continue reading…