
Human | Lifelong learner 📖 | | Sysadmin 💻 | Devops | @LABTIC_CI 's padawan
Abidjan 🇨🇮
Joined April 2015
- Tweets3.2K
- Following1.5K
- Followers839
- Likes5K
Mariio retweeted
Microsoft has a free DevOps learning path built to prepare you for its DevOps Engineer certification.
It covers the core skills you'll actually work with as a DevOps Engineer:
→ Source control & collaboration
→ Containers, Kubernetes & infrastructure
→ CI/CD, testing & release automation
→ Infrastructure as Code & configuration
→ Security, compliance & monitoring
→ AZ-400 exam preparation
The learning content is free on Microsoft Learn. The certification requires passing the exam separately.
learn.microsoft.com/en-us/tr…
Mariio retweeted
Boa Christ ( 18 ans ) fait partie de ces joueurs qu’on croise rarement dans le football moderne.
Droitier au profil technique affirmé, il évolue naturellement au poste de numéro dix, avec la capacité de glisser sur les ailes selon les besoins du jeu.
Son style est reconnaissable entre mille : soyeux, gracieux, il évolue avec une aisance rare dans les petits espaces, où il aime combiner et faire sortir des gestes extraordinaires.
Sa facilité à distribuer le jeu et son sens de la passe en font un véritable créateur, capable de faire la différence dans les zones les plus denses du terrain.
Ce qui frappe le plus chez Boa Christ, c’est sa précocité. Dès l’âge de 15 ans, il participait déjà au championnat de troisième division en Côte d’Ivoire, une expérience rare à cet âge qui témoigne d’une maturité footballistique en avance sur son temps.
Bien que positionné comme milieu offensif, Boa Christ possède une vraie capacité à conclure les actions : il peut prendre feu rapidement devant le but, ajoutant une dimension de finisseur à son profil de créateur.
Mariio retweeted
DOCKER IMAGES & LAYERS
A STEP-BY-STEP TUTORIAL
WHAT IS A DOCKER IMAGE
-> A Docker image is a read-only template used to create containers
-> It contains application code, runtime, libraries, and dependencies
-> Images are portable and can run consistently across environments
-> Built using a Dockerfile
WHAT ARE DOCKER LAYERS
-> Docker images are composed of multiple layers
-> Each layer represents a change or instruction
-> Layers are stacked to form the final image
-> All layers are immutable once created
HOW DOCKER IMAGES ARE BUILT
-> Docker reads the Dockerfile
-> Executes instructions one by one
-> Each instruction creates a new layer
-> Layers are combined into a final image
COMMON DOCKERFILE INSTRUCTIONS AND LAYERS
-> FROM
-> Defines the base image
-> Creates the first layer
-> RUN
-> Executes commands
-> Adds a new layer with changes
-> COPY / ADD
-> Transfers files into the image
-> Creates a new layer
-> ENV
-> Sets environment variables
-> Adds metadata layer
-> WORKDIR
-> Sets working directory
-> Affects subsequent instructions
-> CMD / ENTRYPOINT
-> Defines container startup behavior
-> Final layer configuration
LAYERED FILESYSTEM EXPLAINED
-> Each layer is read-only
-> Layers are stacked on top of each other
-> Docker merges them into a single unified filesystem
-> Containers add a writable layer on top
WRITABLE CONTAINER LAYER
-> Created when a container starts
-> Stores runtime changes
-> Includes logs, temporary files, and modifications
-> Removed when the container is deleted
DOCKER LAYER CACHING
-> Docker caches each layer during build
-> If nothing changes, cached layers are reused
-> Improves build performance
-> Changing one layer invalidates subsequent layers
LAYER REUSE AND SHARING
-> Multiple images can share common layers
-> Saves disk space and bandwidth
-> Faster image pulls and builds
-> Encourages reuse of base images
WHY DOCKER LAYERS MATTER
-> Efficient storage management
-> Faster build times
-> Faster deployment and scaling
-> Easy updates by rebuilding only changed layers
BEST PRACTICES FOR USING LAYERS
-> Use minimal base images
-> Combine RUN instructions where possible
-> Order instructions for optimal caching
-> Avoid unnecessary files in the image
-> Use multi-stage builds for cleaner images
FINAL SUMMARY
-> Docker images are built from layered instructions
-> Each layer is immutable and reusable
-> Containers run on top of these layers with a writable layer
-> Efficient layering improves speed, storage, and scalability
LEARN DOCKER IN DEPTH
-> Grab the Docker Mastery eBook
-> codewithdhanian.gumroad.com/…
Mariio retweeted
Learn Coding by playing games
1. Kubernetes
k8sgames.com
2. DevOps
devops.games
3. Linux
overthewire.org
4. Git
ohmygit.org
5. Python
codecombat.com
6. CSS & HTML
codepip.com
7. Cybersecurity
picoctf.org
8. Mobile Coding (like Duolingo)
sololearn.com
9. For Complete Beginners
scratch.mit.edu
10. 25+ Programming Languages
codingame.com
Mariio retweeted
Local AWS emulator alternative
github.com/Nahuel990/minista…
Mariio retweeted
Generates architecture diagrams from Terraform code
github.com/patrickchugh/terr…
Mariio retweeted
Vous négociez bientôt votre salaire au Bénin, en CIV ou au Sénégal ? J’ai soumis les données de salaire minimum de TOUTE l’Afrique à une IA et 30 min plus tard → un calculateur gratuit qui vous dit EN 5 SECONDES si vous gagnez ce que vous méritez.
🔗 calsal.vercel.app/
Mariio retweeted
Uploading large files to S3 using traditional single-request methods can be pretty challenging.
Network interruptions can happen, wasting bandwidth and time, and it gets pretty unreliable as files get bigger.
Here, Chisom teaches you how to upload large objects to S3 with AWS CLI multipart upload.
freecodecamp.org/news/how-to…
Mariio retweeted
Production Kubernetes cluster is down. Your manager is asking for updates every 5 minutes.
Here’s your step-by-step troubleshooting playbook:
Step 1: Get your bearings
Check where you are: kubectl config current-context
See all contexts: kubectl config get-contexts
Switch if needed: kubectl config use-context name
List namespaces: kubectl get ns
Step 2: See the big picture
Node health: kubectl get nodes
All pods: kubectl get pods -A
Recent events: kubectl get events –sort-by=.metadata.creationTimestamp -A
This tells you if it’s a cluster-wide issue or isolated problem.
Step 3: Focus on the failing pod
Get details: kubectl describe pod podname -n namespace
Check logs: kubectl logs podname -n namespace
Get inside: kubectl exec -it podname -n namespace – /bin/sh
Step 4: Check health probes
Look for probe failures in the describe output
Test probe endpoint: kubectl exec -it podname -n namespace – curl localhost:port/health
Step 5: Check deployments and rollouts
Rollout status: kubectl rollout status deployment/name -n namespace
View history: kubectl rollout history deployment/name -n namespace
Rollback: kubectl rollout undo deployment/name -n namespace
Step 6: Verify networking
List services: kubectl get svc -n namespace
Check endpoints: kubectl get endpoints -n namespace
Test DNS: kubectl exec -it podname – nslookup servicename
Step 7: Quick fixes that work
Restart deployment: kubectl rollout restart deployment/name -n namespace
Delete problematic pod: kubectl delete pod podname -n namespace
The key is following the steps in order, not jumping around randomly.
Mariio retweeted
From TCP to HTTP, the full course, in its full almost-5-hour-glory, is now up for free on YouTube. Thanks Prime.
Mariio retweeted
I switched to DevOps Engineering 4 years ago!
It was the best career move I ever made.
If you want to start today, here's a roadmap:
Mariio retweeted
Not a joke, many Cloud Engineers don’t fully understand Internet and NAT Gateway differences or their implications.
Here, I’ve made this to help you better understand.
55K+ read my DevOps and Cloud newsletter: techopsexamples.com/subscrib…
What do we cover:
DevOps, Cloud, Kubernetes, IaC, GitOps, MLOps
🔁 Consider a Repost if this is helpful
Mariio retweeted
This website offers a remote private Linux machine for learning, check it out now 👇
linuxzoo.net/
Mariio retweeted
You're tasked with monitoring your fleet of 10,000 servers.
"Have every server report its CPU usage every second to a central PostgreSQL database. You'll get a nice table of (timestamp, server_id, cpu_usage)."
This plan will work for about 15 minutes, until your database disk fills up and its write performance grinds to a halt. 🧵































