You might be saying to yourself, “but I have rootless containers right now with Docker - I run my docker commands as a regular user and it works all the time.” Even though you are executing the docker command line tool without root, the docker daemon is executing those requests as root on your behalf […]
After my previous article on zombie processes I was curious to see if and how they can affect containers running in a Kubernetes (K8S) cluster.
Zombie processes, a short definition
The first step is an orphaned process, a process that has lost his parent.
Suppose the parent process terminates, either intentionally (because the program logic has determined that it should exit), or caused by a user action (e.g. the user killed the process). What happens then to its children? They no longer have a parent process, so they become “orphaned” (this is the actual technical term).
Recently I answered a question on Stack Overflow
How to use multiple image tags with docker-compose?
The validated answer was based on
extends, but it cannot by used anymore in Compose file format
3.x. As suggested by a user, the Extension fields capability added in the version
3.4 of Docker Compose can replace it to achieve the same goal: reuse a single definition to set several tags.