A while back I wrote a post about selecting a base Docker image for Node.js. In that post, I talked about the size difference of the default build for Node.js and the smaller, “slim” and “alpine” builds. The difference can be significant: 650MB for the full image, vs 50MB for the Alpine Linux version. However, […]
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 […]