It’s tempting to use the “:latest” tag of an image when you first get started with Docker and pulling images from DockerHub. After all, who wouldn’t want the latest and greatest version of MongoDB, Node.js, Redis, etc, when they start a project? But this is a guaranteed way to ruin your life, destroy your productivity […]
and once it’s in production, how do I manage, monitor and scale when I need to? These are questions I’ve often been asked, and have asked several times. They are not questions for which I’ve had a good answer, though. Until I spoke with Elton Stoneman from the Docker DevRel team, that is.
Sometimes it seems like it’s impossible to learn the new stuff without breaking your existing work… installing new versions of Node.js, updating Babel.js plugins, enabling experimental features with command-line flags? Nope. It’s far too easy to break things in your current project. But I’ve been working on something that might help make this easier. Before […]
A few days ago I deleted all of my Docker containers, images and data volumes on my development laptop… wiped clean off my hard drive. By accident. And yes, I panicked! But after a moment, the panic stopped; gone instantly after I realized that when it comes to Docker and containers, I’ve been doing it wrong.
In February, I launched the first of my WatchMeCode: Live! sessions on Docker. This is a series where I do a live webinar-style session of talking about code, providing commentary and getting live Q&A from the audience at the end. For March 2017, I’m preparing another session on the ever-so-frustrating npm delay in Docker. What […]