Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 1 min read

4 Docker Commands I Use Almost Every Day (And You Probably Will Too)

When I first started using Docker, I kept searching for the same commands over and over again. Eventually, I realized that I only needed a handful of commands for 90% of my daily work. Here are the four Docker commands

4 Docker Commands I Use Almost Every Day (And You Probably Will Too)

When I first started using Docker, I kept searching for the same commands over and over again.

Eventually, I realized that I only needed a handful of commands for 90% of my daily work.

Here are the four Docker commands I use the most.

1. Build an Image

docker build -t myapp:v1 .

This command creates a Docker image from your Dockerfile.

I always use version tags instead of latest because it makes deployments easier to track and roll back.

2. Run a Container

docker run -d -p 8080:8080 --name myapp_instance myapp:v1

What this does:

  • Runs the container in the background
  • Maps port 8080 on your machine to the container
  • Gives the container a readable name

Instead of random container IDs, I can simply reference myapp_instance.

3. Monitor What's Happening

docker ps

Shows all running containers.

Need to inspect logs?

docker logs -f myapp_instance

The -f flag streams logs in real time, which is incredibly useful when debugging startup issues.

4. Stop and Remove Cleanly

docker stop myapp_instance && docker rm myapp_instance

One command.

No leftover containers.

No unnecessary clutter.

A Small Habit That Saves Time

I almost never use anonymous containers during development.

Naming containers makes debugging, logging, restarting, and scripting much easier.

It seems like a tiny habit, but it saves a surprising amount of time over the long run.

Quick Reference

docker build -t myapp:v1 .
docker run -d -p 8080:8080 --name myapp_instance myapp:v1
docker ps
docker logs -f myapp_instance
docker stop myapp_instance && docker rm myapp_instance

That's it.

You don't need to memorize dozens of Docker commands.

Master these four first, and you'll already handle most day-to-day Docker workflows with confidence.

If you found this useful, save it for laterβ€”you'll probably need these commands again.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.