Manage Containers Part 2 - RHCSA v9 Review 

I’m so happy to hear that! Best of luck!

All the best

Hi, I use and manage Linux servers on a daily basis so it’s like regular practice. I also have read old Unix books as a resource but now there are plenty of good Linux books out there too.

@@beanologi are you a Linux system admin?

@@nlvon I should be a formal sysadmin one day, that’s my goal, I currently take up smaller projects from others and help teachers who teach IT stuff

So you are telling me that it's hard to get a job even though you know Linux this in-depth?@@beanologi

Edit: youtube isnt showing this users comment for some reason 🙃 but basically someone asked: `So you are telling me that it's hard to get a job even though you know Linux this in-depth? @beanologi ` My answer: I thought about this one for it bit lol. Here's what happened 😅: ( I am not a sarcastic robot by the way, this is just how I frame ideas :D ) The rambled, pseudo-intellectual, answer to your question that also manages to dodge bringing anything new or meaningful to the table but still tries to captivate your mind by trying to sound down to Earth: --- "sure, I guess that is one way to put it. landing a good job is not easy. And... I am not saying that out of negativity tho, it is more/less a fact... and when you succeed you (or anyone in a similar position) really earned it. Yeah, theres the typical advice like having good contacts, portfolios, and other things to be competitive in the job market. But thats all goofy surface-level stuff...we all know what helps and doesn't help and also know how to apply it too. [I keep blabbering]. The point is, you asked a hard question which is good because thats what the interviewers are supposed to do. Take on their persona and show them who's boss. I am sure you are a very capable person and can do it." --- The direct answer and call to action (if you are also looking for a job, which is just an assumption in my head): --- "Yes. Knowing Linux is still good even if it doesn't guarantee a smooth job search. Very few skills do that in practice. Be positive and don't give up. Take a scientific approach to the job hunt and find what works for your situation. Isolate variables and limit negative self-talk to save your attention for the greater goal." --- Reflection time: Okay cool. So what did I learn here by thinking about your question? --- Well, I personally like the direct answer out of the two I shared - We just swallow the hard truth and just get down to business on how to do better. There is often a part of me that likes to dance around the real situation and gets carried away, thinking I am on to something BIG (when I'm not). Knowing this, is generally best to have a balanced outlook and to not get to fancy with how to articulate poetic answers and to simply shut up and take action instead (wow cliche). I can definitely say it feels good to take a shot at a resolving a difficult reality with a spicy hot take but at the end of the day what actually gets done? Pure silence and refusal to question obviously isn't the answer either. I don't need to spell out what is the ultimate answer because everyone's situation is unique. In fact, if I completely missed the mark on what you were asking about and your perspective in life, then the last sentence is probably the only thing that made sense here. --- Anyways... if something here resonated with you, that is awesome. If not, it is still all well, have a wonderful rest of your day :)

Thank you for your comment! Podman uses user namespaces to work rootlessly. So we would use the podman unshare command to start a process in the same user namespace that podman does it’s work in. User namespaces in Linux allow a file to have multiple security identities/ownership and permission info based on the namespace that is accessing the resource. So with that in mind, you can use the podman unshare command to run commands in the podman user namespace to diagnose and correct permission issues for the security identities that the containerized processes see by running commands like chmod or chown. It is different than podman exec because exec is focused on running a command inside of an existing container and we aren’t trying to do anything to the entire podman user namespace. That is at least my understanding so far but I am open to learn more. That was an amazing question! For your second point about podman stop: yeah… I just pretended to be impatient in the video because I wanted to explain more about the process signaling that the stop command does and how bash traps sigterm. You are totally correct that podman stop will time out and run a sigkill as needed 👍 I hope this information was helpful. Thanks for coming to the channel!

In most cases, using ':Z' will be sufficient as it will relabel the contents of the target directory when you start the container. For complex, long-term, setups, it might be useful to set a default fcontext with semanage and omit ':Z' to get more fine grained control over the labels but you will also need to remember to run restorecon. I personally haven't needed to manage the fcontext that deeply when using podman but it is valuable to be aware of in case you are trying an interesting configuration.