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…
At Docker, we strive to create tools of mass innovation. But what exactly is Docker? And how can it benefit both your developers looking to build applications quickly and your IT team looking to manage the IT environment? As part of our mission to educate practitioners on Docker and revolutionize the way that they build, ship and run their applications, Technical Evangelist Mike Coleman and myself presented a Docker 101 webinar.
Jérôme Petazzoni, Docker’s tinkerer extraordinaire, has been running full day on container orchestration with the full Docker stack. The whole workshop uses a demo application using DockerCoin (not a real currency, he tells us). It’s got with web frontends, web services, background workers, and stateful data stores. This is all to give you the experience of running a full scale app in production.
When we released Docker 1.10 and Docker Compose 1.6 on February 4th, we provided you with an easy way to build a fully featured and scalable app. It’s amazing what you can do with just one simple file. I am constantly impressed what a docker-compose up gets you now. Networks and Volumes are now first class citizens of Docker Compose. That gives you a lot of control, allowing you to for instance put individual services on more than one network, and easily share volumes.