DEV Community: Harikrishnan N

Docker Image creation and pushing to DockerHub (Step-by-Step!) 🐳

Harikrishnan N — Mon, 28 Apr 2025 15:43:01 +0000

Hey Devs! 👋
In this post, let’s learn how to create your own Docker image and upload it to DockerHub like a pro! 🐳
I’ll keep it super simple — plus, I’ll tell you where you can add screenshots to make the post even cooler!

⸻

🛠️ Step 1: Create Your Project

👉 Start with a simple app/project.
Example structure:

/my-app
 ├── app.py
 └── requirements.txt

⸻

🐳 Step 2: Create a Dockerfile

Inside your project folder, create a file named Dockerfile (no extension).
Example Dockerfile:

# Use an official Python image
FROM python:3.11-slim

# Set working directory
WORKDIR /app

# Copy app files
COPY . .

# Install dependencies
RUN pip install -r requirements.txt

# Run the app
CMD ["python", "app.py"]

⸻

🏗️ Step 3: Build the Docker Image

Now, let’s build your image! Run this in your terminal:

docker build -t your_dockerhub_username/your-image-name:tag .

Example:

docker build -t SysSyncer/hello-world-py:latest .

⸻

🕵️‍♂️ Step 4: Verify Your Image

Check if your image is created:

docker images

⸻

🔐 Step 5: Login to DockerHub

If you haven’t already, login to your DockerHub account:

docker login

It will ask for your username and password.

⸻

📤 Step 6: Push the Image to DockerHub

Now push your image to the cloud!

docker push your_dockerhub_username/your-image-name:tag

Example:

docker push SysSyncer/hello-world-py:latest

⸻

🎉 Step 7: Done! View Your Image on DockerHub

Go to https://hub.docker.com/ and you’ll see your freshly pushed image under Repositories!

⸻

📋 Full Command Summary

# Build
docker build -t your_dockerhub_username/your-image-name:tag .

# Check Image
docker images

# Login
docker login

# Push
docker push your_dockerhub_username/your-image-name:tag

⸻

⚡ Bonus Tip: Tagging Latest

Want your users to always get the latest version?
Add another tag:

docker tag your_dockerhub_username/your-image-name:v1 your_dockerhub_username/your-image-name:latest
docker push your_dockerhub_username/your-image-name:latest

⸻

🎯 Wrapping Up

And that’s it, champ! 🏆
You just built and published your first Docker image to DockerHub!
Imagine millions of servers now being able to pull and run your image with just:

docker pull your_dockerhub_username/your-image-name:tag

Pretty cool, right? 😎🐳

🚀 Level Up Your GitHub Game: Advanced Git Commands You Should Know!

Harikrishnan N — Mon, 28 Apr 2025 15:21:14 +0000

Hey devs! 👋

We all know the basics: git clone, git commit, git push...

But Git has superpowers most people don't use! 💥

Let's dive into some advanced Git commands that'll seriously upgrade your workflow.

1. `git cherry-pick <commit-hash>`

🔹 Use case: Pick a single commit from one branch and apply it to another.

git cherry-pick abc1234

✅ No need to merge the whole branch — just grab what you need!

2. `git stash save "message"`

🔹 Use case: Pause your work and jump to another task without losing changes.

git stash save "WIP: fixing bug"

Then later:

git stash pop

✅ Instantly resume where you left off!

3. `git rebase -i HEAD~n`

🔹 Use case: Interactive rebase to clean up your messy commit history.

git rebase -i HEAD~5

You'll be able to squash, edit, or delete commits like a boss. 🧹

4. `git reflog`

🔹 Use case: Lost a commit? Deleted a branch?

git reflog

✅ Find the commit ID and bring it back. Git never forgets! 😉

5. `git reset --soft HEAD~1`

🔹 Use case: Undo the last commit, but keep your changes in the staging area.

git reset --soft HEAD~1

✅ Great when you realize, "Oops, wrong commit message!"

6. `git bisect`

🔹 Use case: Find which commit broke your code by binary search! 🔥

git bisect start
git bisect bad
git bisect good <commit-hash>

Git will now guide you step-by-step to find the guilty commit.

7. `git remote prune origin`

🔹 Use case: Clean up branches that were deleted on GitHub but still show locally.

git remote prune origin

✅ Keep your repo fresh and tidy!

8. `git shortlog -s -n`

🔹 Use case: See who contributed the most (or least) to your project.

git shortlog -s -n

✅ Fun way to spot the hidden heroes on your team! 🌟

✨ Bonus Tip: Aliases = Speed Boost

Tired of typing long commands?

Set an alias like:

git config --global alias.co checkout
git config --global alias.br branch
git config --global alias.cm "commit -m"

Now you can simply run git co main instead of git checkout main! 🚀

🎯 Final Words

Git isn't just a tool — it's a superpower when you know how to use it well.

Master these advanced commands and Git Good! 😎

🐳 What is Docker, How It Works, and Why We Need It (In Simple Terms with Fun Analogies)

Harikrishnan N — Fri, 25 Apr 2025 19:23:39 +0000

Hey everyone! 👋

Today, I want to talk about Docker — a tool that might seem complicated at first but becomes super clear once you look at it through the right lens.

If you've ever built or run software, you've probably run into this problem:

“It worked on my machine! Why doesn’t it work on yours?”

That’s where Docker comes to the rescue 🚀.

🧠 What is Docker?

Docker is like a magic shipping container for your applications.

Imagine you’re shipping a cake 🎂. You wouldn’t want to just toss it into the delivery truck — it might break, get ruined, or melt. Instead, you’d put it into a sturdy container that keeps it safe and fresh, no matter where it’s going.

Docker does the same thing for software. It packages your app with everything it needs to run — the code, the libraries, the dependencies, and even the environment itself. Then, that package can run anywhere — your laptop, your friend’s laptop, a server, or the cloud — and it’ll behave exactly the same.

🛠 How Docker Works (In a Nutshell)

Think of your computer as a big kitchen 🧑‍🍳. Normally, when you run apps, they all share the same kitchen. But what if one app needs a gas stove and another needs an electric one?

That’s where Docker steps in. It gives each app its own mini-kitchen, perfectly set up with everything it needs — isolated, clean, and reproducible.

These mini-kitchens are called containers. And they’re all created based on images — like blueprints of the kitchen setup.

🤔 Why Do We Need Docker?

Here’s why Docker has become so popular:

Consistency – It works the same in development, testing, and production.
Speed – Containers start in seconds.
Isolation – Apps don’t mess with each other.
Efficiency – Uses less memory and storage than full virtual machines.
Scalability – Easy to spin up more copies when demand grows.

🔟 Top 10 Docker Commands with Real-World Analogies

Let’s break down the most commonly used Docker commands with simple analogies:

1. `docker build`

📦 Analogy: Baking a cake from a recipe

💬 "Build a Docker image from a Dockerfile, which is your recipe."

docker build -t my-app .

2. `docker run`

🚀 Analogy: Starting the oven to bake the cake

💬 "Run a container from an image — basically launch your mini-kitchen."

docker run -d -p 3000:3000 my-app

3. `docker ps`

🔍 Analogy: Checking what’s currently cooking in your kitchen

💬 "See all the containers that are currently running."

docker ps

4. `docker stop`

🛑 Analogy: Turning off the oven

💬 "Stop a running container."

docker stop container_id

5. `docker rm`

🧹 Analogy: Throwing away the old kitchen setup

💬 "Remove a stopped container to clean up."

docker rm container_id

6. `docker rmi`

🗑️ Analogy: Tossing the cake recipe

💬 "Remove an image you no longer need."

docker rmi image_name

7. `docker pull`

📥 Analogy: Downloading a cake recipe from the internet

💬 "Get an image from Docker Hub or another registry."

docker pull node

8. `docker exec`

🧑‍🍳 Analogy: Stepping into the mini-kitchen to do something

💬 "Run a command inside a running container."

docker exec -it container_id bash

9. `docker logs`

📜 Analogy: Reading the cooking instructions or oven history

💬 "See the logs/output from a running container."

docker logs container_id

10. `docker-compose up`

🏗️ Analogy: Setting up multiple kitchens from a master plan

💬 "Start multiple containers defined in a docker-compose.yml file — great for apps with databases, frontends, etc."

docker-compose up

🧁 Final Thoughts

Docker might sound techy, but it's just a clever way to package and run software so that everything works everywhere. Whether you’re a beginner building your first web app or an enterprise deploying at scale — Docker makes your life easier.

Once you learn it, you’ll wonder how you ever worked without it.

Just remember — every time you run docker run, you’re spinning up your own little kitchen 🍳.

Happy Dockering! 🐳✨

Git Commands Explained with Quick Analogies

Harikrishnan N — Thu, 24 Apr 2025 10:19:46 +0000

If Git feels like magic sometimes, here’s a cheat sheet that breaks it down with simple analogies. Think of Git as your time-traveling journal for code. Here's how the commands work, in human terms

🔧 git init
"Starting a journal"
You’re opening a fresh notebook to begin tracking your code changes.
_
➕ git add <filename>
"Marking a page for publishing"
_You’ve written something and now you're folding the corner of the page to say, "This is worth saving."

📝 git commit -m "<message>"
"Locking it in with a title"
You give the saved page a name and archive it in your notebook.

🌿 git branch
"Looking at alternate storylines"
See the different timelines your project is exploring.

🌱 git branch <new_branch_name>
"Starting a new storyline"
You begin a new chapter without messing up the main one.

🔍 git status
"Asking, 'What’s changed?'"
You check what’s written, saved, or still in draft.

📜 git log
"Flipping back through your journal"
Look at every change you’ve ever made, in order.

🕵️ git blame <filename>
"Who wrote this line?"
Track down who changed what and when — no judgment, just facts.

🔄 git checkout <branch_name>
"Switching to a different timeline"
Jump into another version of your project.

📬 git fetch
"Checking your mailbox"
You peek at updates from the remote repo but don’t open them yet.

🤝 git merge <branch>
"Combining two timelines"
Bring changes from another storyline into your current one — without rewriting history.

🌐 git pull
"Check your mail and apply the updates"
You get the latest changes and paste them right into your notebook.

❌ git rm --cached *
"Unmarking saved pages"
You tell Git to stop tracking files — like removing sticky notes without deleting the actual pages.

🔧 git config --list
"Looking at your Git settings"
See your preferences and ID cards Git uses for tracking.

💼 git stash
"Temporarily hiding your work"
Tuck your changes in a drawer so you can switch tasks, then bring them back later.

🕰️ git reset --hard HEAD~1
"Undo like you mean it"
You rip out your last journal page — poof, it’s gone. Use with care.

Feel like a Git wizard yet? Keep this as your spellbook. 🧙‍♂️✨

DEV Community: Harikrishnan N

Docker Image creation and pushing to DockerHub (Step-by-Step!) 🐳

🚀 Level Up Your GitHub Game: Advanced Git Commands You Should Know!

1. git cherry-pick <commit-hash>

2. git stash save "message"

3. git rebase -i HEAD~n

4. git reflog

5. git reset --soft HEAD~1

6. git bisect

7. git remote prune origin

8. git shortlog -s -n