If you’ve ever worked with Node.js, you’ve dealt with the joy which is node_modules. Thousands of files slowly churning on your hard drive. Even more slowly if you’re trying to delete them. Want to make them easier to manage? Learn how Dev Containers can help.

Over the last few weeks, I’ve had a lot of questions about publishing images to registries using GitHub Actions. Today, I’ll explore the answer showing how to do this with registries in both Azure and GitHub. Along the way, I’ll also demonstrate how to use GitHub’s OIDC integration with Azure.

Moving to Apple Silicon can introduce challenges if you’re using x64-based containers. Sometimes, emulation is the answer. When it’s not, we can combine some Docker features with some bash scripting to create an optimized container that works well for both platforms.

It’s a best practice to use private registries such as Azure Container Registry with container solutions on Azure. There’s very little guidance if you’re considering using a different registry to store your images. In this post, we’re explore how to use other private registries, such as the GitHub packages Container Registry.

There are lots of options for running containers in Azure, such as Azure Container Apps, Azure Container Instances, Kubernetes, Functions, and App Services. Each offering provides different features to support different scenarios, so it’s important to understand some of the container options that Azure provides today.