This morning, a colleague noticed an issue with a Docker-based workload. I stepped in and checked—an upgrade hadn't migrated the database schema, and everything was failing. I manually ran the command in the container and resolved the issue.
The colleague couldn't understand what had happened. He asked me to explain, so I showed him the procedure.
Like many others, he was fascinated by how easily a "docker compose up -d" can set up a service, but this unfortunately hides complexities that, without adequate knowledge of what's underneath, can make the setup extremely fragile.
These tools are powerful, but we shouldn't make the mistake of thinking that understanding the underlying tools is no longer necessary.
@stefano Very true. If you are an Admin or SRE or generally an Ops person, you should also know what and how Docker abstracts behind the scenes, for troubleshooting purposes for example. Or for better integration and automations of the tools.