DevOps Shortcuts for Linux Docker Kubernetes Git

🚀 Troubleshooting ImagePullBackOff in EKS A DevOps Lesson Learned while building an end-to-end DevOps CI/CD project, I encountered a frustrating error: ImagePullBackOff on Kubernetes despite the image existing locally and on Docker Hub. The Issue: ❌ My EKS cluster was running x86_64 (AMD64) nodes, but I was building Docker images on my ARM64 Mac. Kubernetes couldn't find a matching platform in the image manifest. The Solution: ✅ Build images for the correct architecture: docker buildx build --platform linux/amd64 -t username/image:tag --push . Or build for multiple platforms for maximum portability: docker buildx build --platform linux/amd64,linux/arm64 -t username/image:tag --push . Key Takeaway: Always verify your cluster node architecture and ensure your container images match. A simple kubectl get nodes can save hours of debugging! Pro Tip: Use docker buildx for multi-platform builds in production pipelines. #DevOps #Kubernetes #EKS #Docker #CICD #TroubleShooting #CloudNative

Bash Scripting for DevOps — Part 11/? Till now, I was passing values using environment variables. That worked. But I realized something. Sometimes, I don’t want to set variables separately.I just want to pass values directly when running the script. That’s where arguments come in. In Bash, we can pass values like this: ./deploy.sh staging Inside the script, we can access it using: echo "Deploying to $1 environment" Here, $1 means the first argument. So if I run: ./deploy.sh prod It becomes: Deploying to prod environment This makes scripts much more flexible. Instead of editing the script or setting variables, I can just pass what I need at runtime. This is used a lot in real DevOps workflows: • passing environment names • passing versions or tags • controlling script behavior dynamically Small change. But now the script feels more like a real tool, not just a fixed set of commands. #DevOps #BashScripting #Linux #Automation #DevOpsJourney #LearningInPublic

Git Commands Every DevOps Engineer Should Know! Here's a visual guide to some essential Git commands that power your daily workflows: 1. git commit - Saves your changes with a message 2. git branch feature - Creates a new branch called "feature" 3. git checkout feature - Switches to the feature branch 4. git checkout main - Switches back to the main branch 5. git merge feature - Merges feature branch into main (Fast-forward!) 6. git revert HEAD - Undoes the last commit safely 7. git rebase main - Replays commits on top of another branch 8. git reset HEAD~1 - Moves the branch pointer back 9. git cherry-pick main - Applies a specific commit to current branch 10. git log - Shows the commit history with author and timestamps The visual Git graph shows how branches split, merge, and evolve. Understanding these commands helps you manage code efficiently in any DevOps pipeline. Which Git command do you use the most? #DevOps #Git #VersionControl #CI_CD #CloudNative #Linux #TechLearning

☝️Headline: 🚀 21 Days Down, 79 to Go! #100DaysOfDevOps Challenge Body: Today marked a major shift in my DevOps journey—Git! 🛤️ As part of the KodeKloud 100 Days of DevOps challenge, Day 21 was all about setting up a Bare Git Repository on a storage server. Key Takeaways: ✅ SSH into storage servers to set up version control infrastructure. ✅ Understanding that --bare repositories are the backbone of central, collaborative workflows. ✅ Configuring remote repositories for team projects. It's amazing how much I've learned about Git and Linux in just three weeks. #DevOps #Git #KodeKloud #LearningJourney #VersionControl #100DaysOfDevOps

Day 30: Git Hard Reset & History Cleanup | #100DaysOfDevOps Worked on cleaning up a Git repository by removing unwanted test commits and resetting the commit history to a stable point. A hands-on task to understand how rewriting Git history works and why it’s important to maintain a clean and meaningful commit history in repositories. Used git reset --hard to move the branch back to a specific commit and git push --force to update the remote repository. 📌 Blog: https://lnkd.in/gu3GXDyx #DevOps #Git #VersionControl #Linux #100DaysOfDevOps

After years of working with DevOps tools, I realized that we use a core set of commands almost every single day, yet they’re rarely documented in one place. So I’ve started curating everything i.e Git, Terraform, Kubernetes, Linux and more into simple, practical cheat sheets on Hashnode.....with many more to come 🙌 . You can check it out here👇 https://lnkd.in/dWfnY9q2 . . Feel free to explore anytime and share your feedback! . #DevOps #Git #Terraform #Hashnode #LearningInPublic #TechBlog

🐳 Docker Compose Essential Training — Engine v29 | Compose v5 Hands-on Lab I just published Guide #2 of the Essential Training Series — a practical, hands-on Docker Compose lab that I personally tested command by command before sharing. 📋 What's inside: • 8 exercises covering the core Docker Compose fundamentals • Services, networks, volumes and environment management • Build workflows with Dockerfile and live reload • Health checks and correct startup ordering • Profiles for optional services • Scaling services and resource limits • Debugging with logs, exec and compose config 🔧 Tested on: • Docker Engine v29.4 — Compose v5.1.2 (latest) • WSL2 on Windows — HP i3, 20GB RAM • Real commands, real errors, real fixes This is not a copy-paste from the docs. Every exercise was validated hands-on before being shared. 📎 PDF attached — free to download and use. 📁 Exercise files on GitHub: https://lnkd.in/dhVQ5BVN 🚀 More coming soon: ✅ Docker ✅ Docker Compose (this one) ✅ K3s ⏳ Helm ⏳ GitHub Actions CI/CD ⏳ ArgoCD (GitOps) ⏳ Prometheus & Grafana ⏳ Loki + OpenTelemetry If this is useful — share it with someone learning DevOps 🙌 If it is not — drop a comment or send me your feedback. I am still improving it. #DockerCompose #Docker #DevOps #Kubernetes #CloudNative #Linux #LearningInPublic #OpenSource

Day 32: Git Rebase & Clean History | #100DaysOfDevOps Worked on rebasing a feature branch with the master branch in a Git repository to integrate the latest changes without creating a merge commit. A hands-on task to understand how Git rebase helps maintain a clean and linear commit history while preserving all feature branch work. Used git rebase master to replay commits from the feature branch on top of master, followed by a force push to update the remote repository. 📌 Blog: https://lnkd.in/gW5uYZbp #DevOps #Git #VersionControl #Linux #100DaysOfDevOps #GitRebase

🐳 Docker Essential Training — Engine v29 Hands-on Lab I just published my first guide from the Essential Training Series — a practical, hands-on Docker lab that I personally tested command by command before sharing. 📋 What's inside: • 8 exercises covering the core Docker fundamentals • Images, containers, networking, volumes • Multi-stage Dockerfiles & Docker Compose • Every issue I faced during testing is already fixed 🔧 Tested on: • Docker Engine v29 (latest — March 2026) • WSL2 on Windows — HP i3, 20GB RAM • Real commands, real errors, real fixes This is not a copy-paste from the docs. Every exercise was validated hands-on before being shared. 📎 PDF attached — free to download and use. 📁 Exercise files on GitHub: https://lnkd.in/dBpAXt7h 🚀 More coming soon: ✅ Docker (this one) ✅ Docker Compose ✅ K3s ⏳ Helm ⏳ GitHub Actions CI/CD ⏳ ArgoCD (GitOps) ⏳ Prometheus & Grafana ⏳ Loki + OpenTelemetry If this is useful — share it with someone learning DevOps 🙌 If it is not — drop a comment or send me your feedback. I am still improving it. #Docker #DevOps #Kubernetes #CloudNative #Linux #LearningInPublic #OpenSource

Here I am sharing the robust Jenkins CI/CD Pipeline setup on Server. Sharing an architectural visualization of a complete, production-ready CI/CD workflow. This schematic details the secure integration from a GitHub webhook trigger through automated testing, secure SSH deployment to Ubuntu, and zero-downtime PM2 application reloads. Essential for establishing reliable, predictable, and scalable deployment processes. . . . . . . . #DevOps #CICD #Jenkins #NodeJS #PM2 #Ubuntu #SoftwareEngineering #Automation #ProductionEngineering