Umar J.’s Post

🚨 CI Build Success… But Snyk Scan Failed? Faced an interesting issue today in Azure DevOps 👇 ✔️ Docker image was built successfully ❌ But Snyk scan failed with: "SNYK-CLI-0000: Image does not exist for the current platform" At first, it looked like the image wasn’t available… but that wasn’t the real problem. --- 💡 Root Cause: 👉 Platform mismatch (amd64 vs arm64) The image existed, but Snyk couldn’t resolve it for the current platform. --- ✅ Fix: docker build --platform=linux/amd64 -t <image> . And in pipeline: env: DOCKER_DEFAULT_PLATFORM: linux/amd64 --- 🎯 Key Takeaway: Before debugging CI failures, always check: - Platform compatibility - Image tag correctness - Registry availability --- 💭 Small issues like this can consume hours if you don’t spot the pattern early. Sharing this so it saves someone else’s time 🙌 #DevOps #AzureDevOps #Docker #Snyk #CICD #Debugging #LearningInPublic

Check out this Kubernetes project where I implemented and tested Ingress and RBAC from the ground up on a Linux system. This wasn’t just about following instructions it involved breaking configurations, troubleshooting issues, verifying access controls, and observing how networking actually behaves within a live cluster. In this walkthrough, you’ll learn 1 How RBAC enforces permissions inside Kubernetes 2 How Ingress directs external traffic to your services 3 The process of deploying and exposing applications 4 What goes wrong in real scenarios and how to diagnose and resolve it If you're diving into DevOps or Kubernetes, skip passive reading build things yourself, break them, and gain real understanding through practice. Check out the video, take away what helps you, and share your thoughts in the comments. #Kubernetes #DevOps #Cloud #Linux #K8s #RBAC #Ingress #Containers #Docker #PlatformEngineering #SRE #Infrastructure #Automation #LearningByDoing #Tech #CloudComputing #AWS #Engineering #DevLife #IT #HandsOn #BuildInPublic Ahmed Ali Ayman Albasha Anum Fatima Araiz Asim muSharp Vishakha Sadhwani Abdulrahman AL-Alsheikh - Prosci® Shilash M DevOps Insiders

🏌️♂️𝗨𝗣𝗦𝗞𝗜𝗟𝗟 2.0 𝗷𝗼𝘂𝗿𝗻𝗲𝘆 ~ "𝗕𝘂𝗶𝗹𝗱-𝗜𝘁, 𝗕𝗿𝗲𝗮𝗸-𝗜𝘁, 𝗙𝗶𝘅-𝗜𝘁"   Turning chaos into clarity and mistakes into real-world engineering experience 💻 “𝙈𝙮 𝙘𝙤𝙙𝙚 𝙬𝙤𝙧𝙠𝙚𝙙 𝙤𝙣 𝙢𝙮 𝙢𝙖𝙘𝙝𝙞𝙣𝙚” 𝙞𝙨 𝙩𝙝𝙚 𝙘𝙤𝙧𝙥𝙤𝙧𝙖𝙩𝙚 𝙫𝙚𝙧𝙨𝙞𝙤𝙣 𝙤𝙛 “𝙏𝙝𝙚 𝙙𝙤𝙜 𝙖𝙩𝙚 𝙢𝙮 𝙝𝙤𝙢𝙚𝙬𝙤𝙧𝙠.” 🤡 Currently in my #learning phase — diving deep into AWS, Linux, Git, CI/CD, and Cloud/DevOps ☁️ And honestly… real learning starts when things break 😅 You haven’t truly started this journey until you’ve: 🔐 Broken Linux permissions and locked yourself out of a server ⚙️ Spent hours debugging a CI/CD pipeline because of a tiny YAML indentation 🐳 Faced container failures and Docker issues out of nowhere 🌐 Deployed something… and then realized it works only on localhost Fixed an issue and thought: “Okay… now I actually understand what’s happening under the hood.” Here’s what I’m realizing: 🏌️♂️You don’t master DevOps by just reading documentation 🏌️♂️ You master it by troubleshooting, breaking systems, and rebuilding them better 🏌️♂️ Every failed build, misconfigured pipeline, or network issue is part of the learning curve From understanding Linux internals to exploring cloud infrastructure, automation, and system design — this is just the beginning 🚀 #LearningJourney #DevOps #Linux #AWS #CloudEngineering #CI/CD #Upskill #KeepBuilding #GrowthMindset #TechHumor

Before I worked my way into DevOps tools, I’ve been focusing on understanding what actually happens underneath. Deployments aren’t just a button click. - How applications are built and deployed - How they’re hosted (IIS / servers) - How APIs behave when something breaks - How databases respond under load - How logs reveal the real issue Working without a full DevOps toolchain pushed me to learn these fundamentals deeply, which allowed me to understand the core aspects. Now when I look at CI/CD or Docker, I don’t just see tools, I understand the problems they solve. Still building, step by step. #DevOps #Linux #SQL #Backend #SoftwareEngineering #Learning #TechJourney

One thing I understood while learning Docker deeply: A lot of people say Docker is just "packaging an application." But the bigger shift Docker brings is environment consistency. Before containers, one of the biggest engineering problems was: "It works on my machine, but fails elsewhere." Docker changes that by packaging: • application • dependencies • runtime • system libraries into one portable unit. What I found more interesting is that containers are lightweight not because they are "small VMs", but because they share the host OS kernel instead of running a full guest OS. That single design decision is why containers start in seconds while VMs take much longer. This also explains why container security becomes important: shared kernel means isolation matters. The deeper I learn DevOps / DevSecOps, the more I realize many modern engineering decisions start from understanding these fundamentals properly. #DevOps #DevSecOps #Docker #Cloud #Linux #Automation

“Kubernetes is easy… until you try setting it up yourself.” — I built a Kubernetes cluster from scratch on AWS using kubeadm — and instead of “learning Kubernetes”… I ended up debugging it like a production system. 🚨 Things that went wrong: 💥 CRI errors → container runtime wasn’t even working 🛠️ Fix → Reconfigured containerd ⚠️ Cgroup mismatch → kubelet vs containerd conflict 🛠️ Fix → SystemdCgroup = true 🔥 API server (6443) refused connections 🛠️ Fix → Fixed runtime + re-init cluster 🌐 Node stuck in NotReady 🛠️ Fix → Installed Calico (networking layer) ⚡ End result: ✔ Multi-node cluster running ✔ Stable control plane ✔ Pods deployable But here’s the real takeaway 👇 Kubernetes is NOT about running commands. It’s about understanding what breaks… when things go wrong. And honestly — that’s where the real learning happens. This didn’t feel like a lab anymore — this felt like real production debugging. If you're learning Kubernetes: Don’t just follow tutorials. Break things. Fix them. Repeat. That’s where it actually clicks 💡 #Kubernetes #DevOps #AWS #CloudComputing #DevOpsEngineer #CloudEngineer #SRELife #Linux #Docker #CloudNative #Infrastructure #LearningInPublic #BuildInPublic #EngineeringLife

Below, I am sharing some practical insights that I have experienced. If you're new to Docker Hardened Images or experiencing the same issue as me, the information below will assist you. Please refer to the link below to view the available Docker hardened images :- https://lnkd.in/gy-QATjv DHI is utilized in production due to its ultra-lightweight nature and its foundation on Alpine and Debian Linux. The lightweight nature means it doesn't contain sh, apt, curl, sudo, or wget. For further details, check out the link below. https://lnkd.in/gXZ3Whk5 The command to access the DHI container terminal differs from the usual one of 'docker exec -it <unk> container-name> /bin/bash', but it is not effective. 'docker exec -it 'container-name> /bin/sh' is the command used for DHI. To use DHI, it is necessary to log in to 'dhi.io' using your system or cloud terminal, and then execute Compose, build, or pull the DHI image. Take a look at the other sections of the post that is similar to this one 1. https://lnkd.in/gBX6cGyw 2. https://lnkd.in/gNUXSCs7 #Docker #DevOps #Containerization #LearnDevOps #coding [ Docker, DevOps, Containerization, LearnDevOps, coding ]

Below, I am sharing some practical insights that I have experienced. If you're new to Docker Hardened Images or experiencing the same issue as me, the information below will assist you. Please refer to the link below to view the available Docker hardened images :- https://lnkd.in/gy-QATjv DHI is utilized in production due to its ultra-lightweight nature and its foundation on Alpine and Debian Linux. The lightweight nature means it doesn't contain sh, apt, curl, sudo, or wget. For further details, check out the link below. https://lnkd.in/gXZ3Whk5 The command to access the DHI container terminal differs from the usual one of 'docker exec -it <unk> container-name> /bin/bash', but it is not effective. 'docker exec -it 'container-name> /bin/sh' is the command used for DHI. To use DHI, it is necessary to log in to 'dhi.io' using your system or cloud terminal, and then execute Compose, build, or pull the DHI image. Take a look at the other sections of the post that is similar to this one 1. https://lnkd.in/gNUXSCs7 2. https://lnkd.in/gHTYzUZ4 #Docker #DevOps #Containerization #LearnDevOps #coding [ Docker, DevOps, Containerization, LearnDevOps, coding ]

🔥 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗶𝘀 𝗲𝗮𝘀𝘆… 𝘂𝗻𝘁𝗶𝗹 𝗶𝘁 𝗶𝘀𝗻’𝘁 😅 That’s the real Kubernetes experience. At first it looks simple: → Deploy containers → Scale automatically → Self-healing workloads Then reality hits: ❌ Networking issues you can’t see ❌ YAML breaking everything with one typo ❌ RBAC permissions that fail silently ❌ Debugging across pods, nodes, and clusters And you realize: Kubernetes isn’t hard because of commands. It’s hard because it forces you to think in systems. Networking. Security. Distributed architecture. Failure modes. The good news? Everyone struggles at the beginning. Here are resources that actually help: 📚 Kubernetes Official Docs https://lnkd.in/e7Z9_u79 📚 Kubernetes The Hard Way, Kelsey Hightower https://lnkd.in/dAyYVctG 📚 Kubestronaut Roadmap (YouTube) https://lnkd.in/gpARn22q 📚 Killercoda (hands-on labs) https://killercoda.com/ 📚 TechWorld with Nana (YouTube) https://lnkd.in/eEQzGkGe 📚 CKA / CKAD learning paths (Linux Foundation) https://lnkd.in/eY4SXf35 💡 Biggest tip: Don’t try to memorize YAML. Try to understand why things break. That’s when Kubernetes finally clicks. Who else has had a “Kubernetes made me cry” moment? #Kubernetes #DevOps #CloudEngineering #PlatformEngineering #SRE #CloudComputing

Understanding core Docker concepts is essential for anyone working in modern development, DevOps, or cloud environments. From Dockerfiles and images to containers, volumes, networks, and key commands, having clarity on these fundamentals makes it easier to build, deploy, and manage applications with confidence. I’ve put together this quick visual guide to simplify the basics and make Docker concepts easier to understand at a glance. Whether you’re just getting started or revisiting the foundations, strong fundamentals always make a difference. What Docker concept took you the longest to fully understand? Let’s connect and share insights. #Docker #DevOps #CloudComputing #Containerization #SoftwareDevelopment #BackendDevelopment #TechLearning #Programming #Infrastructure #CloudNative #Linux #Developers