Vim Cheat Sheet for Engineers

Unpopular opinion (learned this the hard way): You don’t really understand Kubernetes or Docker… if you don’t understand Linux. I used to focus on tools first: Kubernetes. Docker. Terraform. I could deploy things. Scale things. Monitor things. But when something broke? I was stuck. Because here’s the truth most people skip: 👉 Docker is just Linux containers (namespaces, cgroups) 👉 Kubernetes is just an orchestrator sitting on top of Linux systems 👉 And most automation around it? Powered by Python That realization changed everything for me. So I went back to basics: 🖥️ Linux — processes, memory, networking, permissions 🐍 Python — scripting, automation, control No dashboards. No abstractions. Just fundamentals. And suddenly: ⚡ Debugging Kubernetes issues made sense ⚡ Docker errors weren’t “random” anymore ⚡ I could automate instead of copy-pasting commands Now I don’t just “use” tools — I understand what they’re doing under the hood. That’s the real leverage. 👉 Tools make you productive 👉 Fundamentals make you dependable If you’re serious about SRE / DevOps: Don’t just learn Kubernetes. Learn what Kubernetes is built on. #Linux #Python #Kubernetes #Docker #SRE #DevOps #TechCareers

🚨 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

Title: AI-Guided DevOps Lab: Kubernetes & Docker I come from Software Support. I'm moving into DevOps. And I'm not waiting for a bootcamp to do it. Just pushed a hands-on lab to GitHub — built from scratch, broken multiple times, and fixed with a lot of patience (and AI debugging help): → Docker: built and optimized container images from the ground up → Kubernetes: deployed a self-healing pod, wrestled with YAML and networking → Linux: CLI commands and shell scripting through actual practice, not tutorials AI didn't do the work. It helped me understand why things broke and how to fix them — which is the part most courses skip. Repo link below: [https://lnkd.in/dK4EPZi5] #DevOps #Docker #Kubernetes #Linux #SoftwareEngineering #AI #OpenToWork #GitHub

“𝗗𝗼𝗰𝗸𝗲𝗿 𝗸𝗮 𝗶𝘀𝘀𝘂𝗲 𝗵𝗮𝗶 𝗸𝘆𝗮?” A teammate asked this while debugging. Everything looked fine — but something felt off. Then I paused: 👉 𝗛𝗼𝘄 𝗱𝗼𝗲𝘀 𝗗𝗼𝗰𝗸𝗲𝗿 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘄𝗼𝗿𝗸 𝘂𝗻𝗱𝗲𝗿 𝘁𝗵𝗲 𝗵𝗼𝗼𝗱? When we run: 👉 docker run nginx It feels like CLI directly starts the container. ❌ It doesn’t. Behind the scenes, it sends 𝗥𝗘𝗦𝗧 𝗔𝗣𝗜 𝗰𝗮𝗹𝗹𝘀: • 𝗣𝗢𝗦𝗧 /𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀/𝗰𝗿𝗲𝗮𝘁𝗲 • 𝗣𝗢𝗦𝗧 /𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀/𝘀𝘁𝗮𝗿𝘁 ⚠️ Even on the same machine, this is 𝗡𝗢𝗧 𝗛𝗧𝗧𝗣/𝗧𝗖𝗣. Instead, it uses: 👉 /𝘃𝗮𝗿/𝗿𝘂𝗻/𝗱𝗼𝗰𝗸𝗲𝗿.𝘀𝗼𝗰𝗸 👉 𝗨𝗻𝗶𝘅 𝗗𝗼𝗺𝗮𝗶𝗻 𝗦𝗼𝗰𝗸𝗲𝘁 (𝗜𝗣𝗖) Which means: • Faster communication • No network overhead • Controlled local access The daemon (𝗱𝗼𝗰𝗸𝗲𝗿𝗱) listens, processes, responds. 🔥 𝗗𝗼𝗰𝗸𝗲𝗿 𝗶𝘀𝗻’𝘁 𝗺𝗮𝗴𝗶𝗰 — 𝗶𝘁’𝘀 𝘄𝗲𝗹𝗹-𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗱 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻. 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆: 👉 Understand internals → Debug faster #Docker #DevOps #Containers #Linux DevOps Insiders

💡 Most people learn DevOps… I decided to build one from scratch. So I created my own self-hosted homelab infrastructure 🏠⚙️ --- 🚀 What’s inside? - 🐧 Ubuntu Server - ⚙️ Kubernetes (k3s) for orchestration - 🌐 Nginx as reverse proxy - 📺 Jellyfin (media server) - ☁️ Nextcloud (self-hosted storage) - 🤖 CI/CD using webhooks + bash scripts - 🧠 Custom Python tool to automate media ingestion --- 📊 The architecture (attached below) shows how everything connects — from networking → compute → storage → automation. --- 🔥 What I learned: - Real DevOps is not just tools — it’s how systems interact - Debugging > Tutorials (mount failures, permissions, streaming issues 😅) - Automation makes everything 10x smoother --- 🔗 Project Repo: https://lnkd.in/gZ9G9peh --- Would love to hear your thoughts or suggestions to improve this setup 👇 #DevOps #Kubernetes #Homelab #Linux #Automation #SelfHosted #SRE #Backend

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 ]

🐳 Dockerfile & Docker-Compose — Made Simple Ever felt Docker is complex? Let’s break it down in the easiest way 👇 🔹 Dockerfile Think of it as a recipe 🧾 It defines how your application image is built step by step. 🔹 Docker Compose Think of it as a manager 🎯 It runs multiple containers (app + DB + services) together using one simple file. 💡 In short: Dockerfile = How to build Docker Compose = How to run everything together 🚀 Mastering these two = Strong DevOps foundation Consistency. Scalability. Automation. That’s the power of Docker 💪 👇 Tell me in comments: What’s your biggest challenge in Docker right now? #Docker #Dockerfile #DockerCompose #DevOps #DevOpsEngineer #CloudComputing #Kubernetes #Containerization #Microservices #CICD #Automation #InfrastructureAsCode #AWS #Linux #Programming #TechLearning #Developers #CareerGrowth #CodeLife

If you haven't subscribed to EverythingDevOps as a DevOps Engineer, you're missing out. A newsletter just meant for you. I learned new Linux commands today I've never heard of. Did you know you can use a line of command to convert documents into different formats, instead of going through the website converters online? This is not a paid advertisment by the way. This is just me pointing you in the right direction. #EverythingDevOps #devops #IT #informationtechnology #software #tech #linkedin #linkedinvoices

After a sudden reorganization, your team has just inherited a legacy Docker image with no handover or documentation. The container starts when you run the image, but no ports are exposed, and the logs are unhelpful.  Right now, the application running inside the container is completely inaccessible. Can you find and expose the port? https://lnkd.in/etuyjWMK Happy fixing! #LearnByFixing #DevOps #SRE #Sysadmin #Docker