Docker Thoughts

Recently, I was turned onto Docker after trying to set up NSA’s GHIDRA tool as recommended. GHIDRA docs say if you must run the program on Linux, the recommended operating system is Cent-OS.

I’ve never used Cent-OS, so I figured I’d look for ways to quickly test the tool.

I eventually landed on Docker and learned how to spin up a container running a CentOS image. You can do this with a single BASH command, and it works consistently.

I was shocked to see how stable it ran. I was also surprised at how well Docker meshed within a Linux environment. BASH and Docker seem to be interwoven, allowing users to do lots of work with simple bash commands.

Hypothetically, you could have 10,000 containers all mapped to individual ports on a remote server, and delete them all almost instantaneously by using Linux pipes to redirect stdio and stdin.

The amount of control over large amounts of data, information, and applications is what Docker is all about. Docker allows Linux admins to operate in a elegant fashion versus one that’s synonymous with walls of terminal text.

The Payload

So why am I telling you this? It’s common knowledge, I know. But I found myself Googling lots of the different commands and how to use them. Eventually, some notes were taken, and then were added into one of my projects that attempts to build a customized “knowledge database”.

I will post the notes below, and hopefully you can understand Docker, at a glance, better.

“Im talking PRIMO notes” – Noah Tannenbaum

You Might Also Like

Leave a Reply

Your email address will not be published. Required fields are marked *