When encountering problems in a production environment it is sometimes hard to recreate the issue locally or in a test system. Some issues are actually depending on very specific runtime conditions while others arise from the combination of entries in the database. Generating the right test data is not always easy given that you do not already know what is wrong and just have to confirm it. Testing against a production system usually is not an option (and should not be considered unless you are truly desperate).
In this post, we explain why we built and how we use waitforservices, a small utility to be used in a Docker container, that waits for linked services to be ready.
While there's an official guide for deploying Docker registry 2.0, it doesn't fully describe how to run Docker registry 2.0 in production. We couldn't find a guide on which settings to change and setting up basic authentication had a few hurdles, so we show in this post how we made our setup work.