DEV Community: Rajaram Nivas

# 🚀 Dockerize and Share Your ML Model: Logistic Regression with Iris Dataset

Rajaram Nivas — Mon, 28 Apr 2025 16:30:20 +0000

Have you ever wanted to package your Machine Learning models into a portable container that works anywhere?

Today, I'll show you exactly how I did it — by training a Logistic Regression model on the Iris dataset, visualizing the data, and packaging everything neatly into a Docker image.

Let's dive in! 🏊‍♂️

📦 Project Structure

Here’s how the project folder is organized:

ml-docker-project/
├── Dockerfile
├── model.py
└── Iris.csv

🐳 Dockerfile Breakdown

Here's the Dockerfile that powers the container:

# Use the official Python image as a base
FROM python:3.12-slim

# Set working directory inside the container
WORKDIR /app

# Copy all project files into the container
COPY . .

# Install required Python packages
RUN pip install --no-cache-dir pandas scikit-learn matplotlib joblib

# Run model.py on container start
CMD ["python", "model.py"]

✅ What this Dockerfile does:

Uses a minimal Python 3.12 base image.
Copies all project files.
Installs only essential Python libraries.
Runs the model training script (model.py) when the container starts.

🧪 What `model.py` Does

Here’s what happens inside the model.py script:

Load the Iris dataset from Iris.csv.
Preview dataset shape and first few rows.
Visualize the data with:
- Histograms
- Density plots
Prepare features and labels for modeling.
Split the data into training and testing sets (67%-33%).
Train a Logistic Regression model using scikit-learn.
Evaluate model accuracy and print the result.
Save the trained model to logistic_model.pkl.

All plots are saved silently as .png files (histograms.png, density_plots.png) for future reference. 📊

🔨 How to Build, Tag, and Push the Docker Image

Here’s the step-by-step to package and publish the image:

1️⃣ Build the Docker Image

docker build -t your_dockerhub_username/your_image_name:latest .

(Example: docker build -t viratpk18/24mcr078:latest .)

2️⃣ Log in to DockerHub

docker login

3️⃣ Push the Image to DockerHub

docker push your_dockerhub_username/your_image_name:latest

📤 DockerHub Image Description

When you publish, you can use a description like this:

Title: Logistic Regression on Iris Dataset - Dockerized

Description:

Train a Logistic Regression model on the classic Iris dataset inside a container!

Loads and explores the Iris dataset

Visualizes data (histograms, density plots)

Splits into train/test

Trains a Logistic Regression model

Evaluates and prints accuracy

Saves the trained model (logistic_model.pkl)

Fully reproducible with Docker. Just pull and run!

Pull Command:
docker pull your_dockerhub_username/your_image_name:latest
Run Command:
docker run your_dockerhub_username/your_image_name:latest

💬 Final Thoughts

With just a few simple steps, we can turn a machine learning project into a portable, reproducible, and shareable artifact! 🚀

By using Docker, you ensure that your model can be trained, evaluated, and tested in any environment, without worrying about Python versions, library installations, or messy dependencies.

This is just the beginning — next steps could involve:

Adding a Flask API on top to serve the model.
Building a simple web UI for predictions.
Automating deployments with GitHub Actions.

The possibilities are endless!

If you found this helpful, follow me for more Machine Learning and DevOps content! 💬

Happy Dockering! 🐳

️⃣ #MachineLearning #Docker #Python #IrisDataset #DataScience #DevOps

ADVANCED GIT COMMANDS

Rajaram Nivas — Sat, 26 Apr 2025 02:26:09 +0000

🚀 Level Up with These 10+ Useful Git Commands

By Rajaram

Git is a powerful tool for developers — not just for saving your code, but for managing versions, collaborating, and resolving issues like a pro. In this post, let’s walk through some essential and advanced Git commands that can boost your workflow.

1. 🔍 `git diff`

Purpose: Show changes between files, commits, or branches.

Use Case: Compare your working directory with the index or a previous commit.

git diff

2. 📜 `git log`

Purpose: Display the full commit history.

Use Case: Track changes, find specific commits, or understand project history.

git log

3. 📥 `git clone`

Purpose: Clone a remote repository to your local machine.

git clone https://github.com/rajaramnivas/24MCR080

4. ⬇ `git pull`

Purpose: Fetch and merge changes from the remote repo to your current branch.

git pull origin main

5. ⬆ `git push`

Purpose: Push your local commits to the remote repository.

git push origin main

6. 🕵 `git blame`

Purpose: Show who last modified each line of a file and when.

Use Case: Great for debugging or understanding change history.

git blame ML.txt

7. ⚔ Merge Conflicts (Concept)

Note: Merge conflicts happen when two branches modify the same part of a file.

To simulate a merge conflict:

git checkout -b new-branch
# Make changes, commit them
git checkout main
# Make conflicting changes
git merge new-branch
# Conflict occurs here

You'll need to manually resolve the conflict in the files and commit the resolution.

8. 🌿 `git branch`

Purpose: List, create, or delete branches.

git branch             # List branches  
git branch feature     # Create a branch  
git branch -d feature  # Delete a branch

9. 🚀 `git checkout -b`

Purpose: Create and switch to a new branch in one step.

git checkout -b advanced-git-commands

10. 📁 `.gitignore`

Purpose: Tell Git which files or folders to ignore in version control.

Steps to set up:

Create a .gitignore file in your root directory.
Add patterns of files or folders to ignore.

Example:

*.log
node_modules/
.env

No command is needed — Git will automatically skip tracking files that match the patterns.

💼 Bonus Tip: `git stash`

Purpose: Temporarily save your changes when you're not ready to commit but need to switch branches.

git stash
git stash pop  # To apply them back

🔗 Bonus: GitHub Repo

You can check out the repository related to this guide here:

👉 GitHub - 24MCR080

💡 Final Thoughts

These Git commands may look simple, but mastering them gives you better control, cleaner workflows, and confidence when collaborating with teams. Whether you're debugging, exploring history, or working on features — Git's got your back.

🙌 Thanks for reading!

If you found this helpful, leave a ❤️ or drop your favorite Git command in the comments!

git #github #beginners #productivity #programming

# 🚀 Step-by-Step Git Commands for Beginners (with Visuals)

Rajaram Nivas — Thu, 24 Apr 2025 01:32:39 +0000

If you're just getting started with Git and GitHub, here's a simple, clear guide to walk you through setting up your repository and pushing your changes for the first time!

🛠️ Initialize a Git Repository

git init

🗂️ This creates a new Git repository in your current folder.

Example: initializing in a folder named 24MCR080.

📄 Add a File to the Staging Area

git add 24MCR080-NOTEPAD.txt

📌 Stages 24MCR080-NOTEPAD.txt so it's ready to be committed.

✅ Commit the File

git commit -m "Added Personal Details"

📝 Creates a snapshot of your project with a commit message.

🔍 Check Git Status

git status

👀 View which files are staged, modified, or untracked.

📜 View Commit Log

git log

📚 Shows the history of your commits.

🌐 Add a Remote GitHub Repository

git remote add origin https://github.com/rajaramnivas/24MCR080.git

🔗 Links your local repository to a GitHub remote.

🌿 Check Current Branch

git branch

🧾 Displays your current branch, typically master by default.

🪄 Rename `master` to `main` (Optional but Recommended)

git branch -M main

🎯 Renames the current branch to main for consistency with modern standards.

☁️ Push Code to GitHub (First Time)

git push -u origin main

📤 Pushes the main branch to GitHub and sets it as the default upstream branch.

🖼️ Visuals for Reference

Here are some screenshots that help illustrate the steps:

🔁 Modifying or Adding New Files

When you update existing files or add new ones, repeat the following:

git add .
git commit -m "Your updated message"
git push origin main

📌 This ensures all changes are tracked and synced with your GitHub repo.

🎯 Conclusion

And that’s it! You’ve successfully:

Initialized a Git repo
Committed your work
Connected to GitHub
Pushed your project to the cloud! ☁️