A few days ago I came across a situation where we wanted to execute our CI pipeline locally. This article details the steps to run GitHub actions locally using nektos/act and Docker-in-Docker(dind). Why even bother? While running your CI pipeline locally may not seem so essential, it is definitely helpful for various reasons. The two very valid reasons listed by nektos/act are: Fast Feedback: Rather than having to commit/push every time you want to test out the changes you are making to your .
This is the very first article on this blog about Docker. And I can’t tell you how excited I’m to write it. This is the very beginning of a whole new journey. Alright then, let’s get started. In this article we will be talking about: What is a Registry? Running our first Private Registry Interacting with Registry Pushing an image Pulling the new image What is a Registry?