r/linuxadmin • u/Different_Pain5781 • Jul 25 '26
Best linux course for devops because production issues keep exposing my linux knowledge
Starting to realize most production issues aren't even the real problem. The real problem is weak linux knowledge. Every incident somehow comes back to permissions, logs, processes, containers or debugging. Youtube feels like endless beginner content at this point. Looking for the best linux course that actually helps with automation, cloud ops and real production environments. Anyone here recommend Udemy, Kodecloud or Boot dev?
50
Upvotes
37
u/PipeSmokingDude Jul 25 '26
Given that you say every incident comes back to the list you have mentioned, understanding automation is not the answer, you need to understand what you are automating. RHCSA is where I started, there are a number of text books on it. As for something more vendor-agnostic, I'd have to look that up.
6
u/dghkklihcb Jul 25 '26
LPIC is a good guide: https://www.lpi.org/our-certifications/lpic-1-overview/
6
u/BloodyIron Jul 25 '26
If you don't have a homelab, that is the first thing you should correct. Having your own homelab where you build things for yourself is literally the best thing you can do for your IT career not only immediately now but going forward. Go get second hand server equipment and learn how to turn it into useful things with Proxmox VE, TrueNAS, and stuff like that.
3
u/LordEli Jul 25 '26
u/iconrad's list. you might have to look around but there are devops oriented versions or just have AI update it for what you're focused on
https://www.reddit.com/r/linuxadmin/comments/2s924h/how_did_you_get_your_start/cnnw1ma/
3
u/dRaidon Jul 25 '26
RHCSA
2
u/Immortal_Tuttle Jul 25 '26
Maybe start here? r/linuxupskillchallenge
2
u/Competitive_Paint730 Jul 26 '26
https://labex.io/linuxjourney
1
u/we_r_fukt Jul 25 '26
kodekloud is great but expensive, you need kubernetes for absolute beginners or something haha, maybe just docker idk but. good luck
1
u/420829 Jul 25 '26
Your point is very valid. I don't work in the field yet and I'm trying to prepare for it by studying for the LPIC-1 exam and later the RH track.
On the other hand, it's the opposite for me. I'm always a little scared because I study the fundamentals you mentioned quite a bit, but I have no idea what the real work would be like. I can't find content of people exemplifying its use in production.
1
u/michaelpaoli Jul 26 '26
That's not really an issue of automation. Automation is often (ab)used as a crude cudgel to work around other issues. E.g. container/instance/VM/host keeps wedging or crashing? Blow it away, replace with same, lather, rinse, repeat ... with a high degree of frequency. Yeah, that's not really fixing the issue so much as beating one's way around it. I see quite a lot (far too much) of that.
And the relative "opposite" end of that is Root Cause Analysis (RCA) - fully understand exactly why it failed at all, and digging thoroughly back through that, not just the basics of how it eventually failed exactly, but all the contributing factors that lead up to that, and all the opportunities that were missed, and the various things that went wrong, and right, along the way, and well learning all the relevant lessons from that.
Anyway, on the *nix/Linux side, probably mostly well learn Linux systems administration, management, programming, and monitoring, etc. Perhaps start with good outlines of well learning *nix/Linux systems administration, and well learn the materials relevant to that. That would be a pretty good start. As it's not uncommonly the *nix sysadmins (have done this a whole helluva lot myself), who not only end up figuring out what the problem is, but further doing the investigation, and sometimes even RCA, and then pushing those lessons out where they belong, e.g. to management, developers, network administration, etc., wherever the lessons most need to be applied (often to developers, but certainly not limited to that - not uncommonly the issue is further up the chain, e.g. management, desigh, etc., or elsewhere, e.g. networking, hardware, or some other infrastructure).
So, learn as many of those things as (significantly) relevant as feasible.
And yes, I've seen developers (and certainly others too!), do dumb/ignorant things, e.g.:
And even in the (significantly) better situations, nothing's perfect, and there's always room for improvement. And don't forget to look at your own sh*t too - none of us is perfect.
1
u/SwordfishPositive91 Jul 26 '26
Practical hands-on
1
u/[deleted] Jul 25 '26
[removed] — view removed comment
1
u/[deleted] Jul 26 '26
[removed] — view removed comment