Docker solves environment conflicts with containers

🚀 Debugging Kubernetes Deployment (ImagePullBackOff + Port Fix) | Day 64/100 – DevOps Journey from KodeKloud Today’s task was a real-world debugging scenario — fixing a broken Python Flask app deployment on Kubernetes. 🔹 What I did: - Identified issue: Pod stuck in ImagePullBackOff - Debugged using kubectl describe pod - Fixed incorrect image → poroko/flask-demo-app - Verified app was running on port 5000 using logs - Updated NodePort Service (32345) to match correct targetPort - Successfully restored application access 🚀 ⚙️ Why it matters: This task reflects real production challenges: - Debugging failed deployments - Fixing image/config issues - Aligning service ports with application - These are critical skills for ensuring high availability and quick recovery in production systems. Github :- https://lnkd.in/gnBnU_cv #100DaysOfDevOps #DevOps #Kubernetes #Debugging #CloudNative #Docker #Linux #LearningInPublic #TechCareers #OpenToWork

Before containers, we had a machine. Three services. Three different Python versions. Three different opinions about what should be in /tmp. The solutions were bad. Separate VMs were expensive and slow to spin up. Config management was fragile, Chef and Puppet could get you to "probably right" but not "reliably reproducible." Manual isolation wasn't isolation at all. Docker in 2013 didn't invent anything. cgroups were in the kernel in 2006. Namespaces existed before that. What Docker built was a well-designed interface on top of things Linux already knew how to do, and packaged it in a way developers could actually use. Understanding that history matters for one reason: if you know why containers were invented, you know what they're actually solving, and what they're not. They're excellent at process isolation and dependency management. They're not a security boundary by themselves. The tool is the solution to a specific problem. Know the problem. Tell me, What’s a time when understanding namespaces or cgroups would’ve saved you hours? #Docker #Linux #DevOps #Containers #Infrastructure #CloudNative #SoftwareEngineering #History #opensource

Bash scripting is humbling. I’ve spent the last week feeling like I’m trying to learn a foreign language from a textbook written in 1978. One missed space or a slightly wrong bracket and the whole thing dies with a cryptic error message. It’s a grind. But then I pivoted into Docker this week, and I could actually breathe again. The difference? Context. I’ve been messing with containers in my home lab for a couple of years now—running services like Nextcloud and Valheim. Because I had that "hands-on" history, the theory finally had a place to land. Bash feels like abstract math; Docker feels like building with Legos I already own. The Golden Rule of the Lab: If you’re doing this at home, keep your "Experimental" and "Production" environments strictly separate. There is no faster way to have a household mutiny on your hands than nuking the DNS or the Wi-Fi while you're testing a new script. My "Production" stack (Pi-hole, pfSense, etc.) stays stable so the house stays happy, while the "Experimental" nodes are where I’m allowed to break things. The takeaway: Theoretical study is necessary, but the home lab is where the actual "clicking" happens. If you’re pivoting careers like I am, don't just read the documentation—break something in your own rack. It’s the only way the "foreign language" starts making sense. #DevOps #HomeLab #Linux #Docker #CareerPivot #kubecraft #k8s #kubernetes

🚀 Day 18 – Shell Scripting Level Up! Today I focused on writing cleaner, safer, and reusable shell scripts — a big step from basic scripting to real-world usage 💻 What I learned: ✔️ Writing and calling functions for reusable code ✔️ Using set -euo pipefail for safer scripts ✔️ Handling return values & local variables ✔️ Building a complete system info script One important takeaway: Using set -euo pipefail makes your scripts more reliable and production-ready by preventing silent failures. Key Learnings: Functions = Cleaner & reusable code Strict mode = Safer & error-free scripts Check out my work:https://lnkd.in/g4TvriXU #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #DevOps #ShellScripting #Linux #Automation #Scripting #LearningInPublic #TechJourney #Cloud #Programming #CareerGrowth #ITJobs #Developers #CodeNewbie

💡 Linux Tip: "which" – Know What You’re Actually Running Ever wondered which exact executable runs when you type a command? 🤔 👉 That’s where "which" comes in. Example: "which python" 🔹 It shows the full path of the executable being used 🔹 Helps you understand which version is actually running 💡 Why is this important? Sometimes multiple versions of a tool exist on a system: - Python 2 vs Python 3 - Different Java versions - Custom binaries vs system binaries In such cases, "which" helps you avoid confusion. ⚡ Real-world use cases: ✔ Debugging version conflicts ✔ Verifying environment setup ✔ Checking installed paths 💡 It may look like a small command, but it saves hours of debugging in the right situation. 🚀 Have you ever faced issues due to multiple versions of the same tool? #Linux #DevOps #TechTips #CommandLine #Programming

Moving from Manual to Automated: My Python File Organizer I’ve been spending my time lately diving deep into Python fundamentals, and I just finished a project that perfectly bridges the gap between basic syntax and functional automation: a File Organizer script. The goal was simple: take a cluttered directory and instantly sort files into category-specific folders (Images, Docs, Media, etc.) based on their extensions. What I focused on in this build: Scalable Data Structures: Instead of a simple key-value pair, I implemented the 'extension_map' as a dictionary of lists. This makes the script incredibly easy to maintain and scale as I add more file types. Modern Path Handling: I used 'pathlib' for object-oriented path manipulation. It’s cleaner, more readable, and ensures the script works across Windows, macOS, and Linux. The DevOps Mindset: Beyond just writing the code, I focused on "idempotency" using .mkdir(exist_ok=True) so the script can run repeatedly without errors, and implementing error handling to manage files that are currently in use. This project was a great exercise in nested iteration and dictionary manipulation. It’s a small step, but these are the building blocks for the larger automation and orchestration tasks I’m working toward in Cloud DevOps. Next up: Adding logging to track file movements and perhaps setting this up as a scheduled task! #Python #DevOps #Automation #CloudEngineering #CodingJourney #PythonCrashCourse #SoftwareDevelopment

At some point, running commands stops being enough. You start asking: why am I doing this more than once? I’ve completed the Introduction to Shell Scripting Basics certification from CodeSignal as part of the Mastering Shell Scripting with Bash path. This stage marked a shift from simple execution to structured control—moving from typing commands to building logic that can make decisions and act independently. I worked through variable manipulation, including string handling and arithmetic expansion $((...)), while also navigating Bash’s strict whitespace rules that demand precision. I implemented conditional logic using if-elif-else structures with both numeric and string operators, built and iterated through arrays using different loop strategies, and created reusable functions using positional parameters ($1, $2) and $@ to handle multiple inputs efficiently. The key takeaway is straightforward: automation starts with how well you structure small things. This foundation is what enables everything else in system scripting and DevOps. #ShellScripting #Bash #Linux #Automation #DevOps #SoftwareEngineering #BackendDevelopment #Programming #Coding #TechSkills #ContinuousLearning #Developers #Engineering #CommandLine #Productivity #Scripting #Unix #TechCareer #CodeSignal #brittonnetic CodeSignal https://lnkd.in/dAB9TMRF

💡 Starting Python on Linux? Here’s a Quick Cheat Sheet If you're beginning your journey with Python in a Linux environment, these basic commands are essential 👇 🔹 Run a Python file python3 file.py 🔹 Check Python version python3 --version 🔹 Make a script executable chmod +x file.py 🔹 Run the script directly ./file.py These may look like small steps, but they form the foundation of working with Python in real-world environments—especially in Cloud and DevOps roles. I’m currently learning and transitioning into Cloud & DevOps, and sharing these small but important learnings along the way. 📌 Save this post if you’re just getting started—it might come in handy. #Python #Linux #DevOps #CloudComputing #PythonForBeginners #LinuxCommands #TechLearning #CareerTransition

Worked on a Cloud File Upload System using Python and Flask. The idea was simple—upload and access files securely through a web interface. Set it up inside a virtual machine and handled basic file storage, upload, and retrieval features. This project gave me hands-on experience with backend development, working in a Linux environment, and understanding how file handling works in real applications. Still learning, but this was a good practical step. #Python #Flask #CloudComputing #BackendDevelopment

📜Learning bash scripting taught me something I didn't expect: The gap between understanding something and using something is massive. You can read about variables and functions all day. But the real progress happens when you: → Apply the theory in isolation (write the function, test it, break it) → Connect the concepts (pass parameters, capture input, handle logic) → Build something end-to-end (a real script that solves a real problem) 👇Below is a script I put together that sorts all .txt files in a directory by size, smallest to largest, with input validation built in. Is it the most efficient script? Probably not. But that's the point, efficiency comes with practice, and you can't refine what you haven't built yet! Most people stop at step one and wonder why it's not sticking. Build something, even something small. That's where it lands. What's a skill you learned by just building with it? 💻 #Bash #Scripting #Linux #Tech #DevOps