We who work in Cloud Native organisations have largely solved the problem of the increased complexity in setting up a Kubernetes platform. But there’s something we have not solved: how to make Kubernetes simple for developers to use.
Moving your business to the cloud could mean freeing your organisation from the need to maintain your own antiquated, energy-sucking data centres for everything. Escaping the ever-present threat that a problem in one part of your system could cripple the whole thing. Recruiting—and keeping— smart engineers eager to work with the latest technology.
First, some good news: the DevOps field’s expertise and performance is growing rapidly. Its best practices, like a clear change-approval process, not only improve speed and stability, but also help decrease engineer burnout.
Debugging Docker containers can be a very challenging process. Here, I’ll share a few basic techniques for debugging containers—mostly Docker ones, but the techniques are also valid for many other types of Linux container engines. (The methods I’ll detail here are intended for Linux-based systems.)
Linux capabilities, and how they interact with users and containers, can confuse even experienced engineers. At first it seems like this is fairly straightforward stuff, but it gets complex quickly and the information on exactly what is going on is scattered across many pages, Git repos and blogs, so it can be hard to piece together.