Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

A note on Docker

While systemctl is a common tool for managing services on traditional Linux systems, it is generally not used in Docker containers due to containers’ isolated and self-contained nature.

Docker containers ideally run a single process and therefore don’t require a complex boot phase or process management. The container, in essence, is the process and doesn’t have access to the host system’s init system (including systemd).

Although it’s possible to have access to these commands in a Docker container, it’s usually undesirable to use any kind of service-management system inside of them.

Docker containers ideally contain a single application and launch a single process when they start. For this, no service management is needed – the running container is your service package, and your Docker container essentially is your process.

We don’t recommend a Docker setup that includes multiple processes or...