11th recipe in 2022

Here goes the 11th recipe of 2022. This one of the smallest I have ever written but it was something that I had to use in the past and didn’t remember how to do it. So, this time, it will be a lot easier when I need it again. Learn how to show all the logs for any docker container that you might have running (or completed but still not pruned) in your Gitlab CI/CD job.

10th recipe in 2022

The 10th recipe of 2022 is now available. This one explains how to install liquibase locally in a MacOS and add MySQL driver to it so that you don’t need any other dependencies locally in any of your locally running projects.

9th recipe in 2022

The 9th recipe of 2022 is about Kaniko and problems building Docker images. Have you ever faced this problem “dpkg: error processing package ( — configure)” or similar? If that is the case, then that might be the right recipe for you.

7th recipe in 2022

Here’s one more recipe for something I was not expecting this week. After some upgrades on my MacOS, I started having issues with the usage of kubectl. After some research, it was related to inconsistencies between that and awscli. Long story short, I had to revert the version of kubectl installed and the recipe shows you how I did.

6th recipe in 2022

Here’s another recipe and this one is about K8s and it teaches us how to start a POD on demand based on a Docker image that requires secrets to be able to fetch it.

5th recipe in 2022

This recipe is about docker and docker-compose. Here, you will see how to define different docker compose using the same images and similar dependencies per different project and not needing to remove orphans and not seeing any docker compose orphan containers warning.

4th recipe in 2022

This recipe is something that I have been using in the last 3/4 years that I had a chance for a recent improvement. With that in mind, I also thought it was the appropriate timing to be shared in my blog. So, here it is. Have you ever had the need to have 2 docker containers depending on each other, but where one needs to be “ready” before being used by the other one? If that is the case, this might be useful for you. It shows how to have liquibase depending (and actually waiting for) on mysql before executing its own commands.

3rd recipe in 2022

March of 2022 has just started and with it, here comes a new recipe. This is about serverless and a potentially annoying problem with AWS configurations. If you ever had a problem with profile not found while trying to deploy an AWS lambda with serverless, this might be helpful.

Design a site like this with WordPress.com
Get started