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

Container commands

Now let’s dive deeper into some of the more complicated, but important, commands and command invocations that you may run into when working with Docker.

docker run

Let’s look at a more complex invocation of the docker run command we used earlier:

 docker run --rm --name mywebcontainer -p 80:80 -v /tmp:/usr/share/nginx/html:ro -d nginx
  • --rm: Clean up (remove) this container when it exits.
  • --name mywebcontainer: Give this container a friendly name – mywebcontainer.
  • -p 80:80: Map port 80 of the host to port 80 in the container. The left port number is on the “outside” (the environment running the container), and the right port number represents the “inside” (container) port. For example, -p 4000:80 will map the container’s port 80 to localhost:4000.
  • -v /tmp:/usr/share/nginx/html:ro: Mount a volume – the host environment’s /tmp directory will be mounted into...