Course info
May 19, 2020
1h 47m

Being able to change your systems at a moment's notice and being able to reflect the changing needs of your customers is not possible without systems that can be deployed quickly. In this course, Getting Started with Podman, you’ll gain the ability to use containers that are managed with Podman without the need of elevated privileges. First, you’ll explore what is meant by "Rootless Containers." Next, you’ll discover how Podman can easily and quickly deploy your services. Finally, you’ll learn how to deploy MySQL databases to writable persistent volumes. When you’re finished with this course, you’ll have the skills and knowledge of container management needed to work effectively in a modern DevOps environment.

About the author
About the author

Andrew is a committed evangelist of the Linux Operating System and the concept of community and freedom that it provides. He has worked as a technical trainer since 1995 and has taught throughout the world, including Australia, the US, Germany and Eastern Europe. Andrew started teaching Linux in 2004 when Novell acquired SUSE and has been a long time supporter of Novell and provides SYSOP support the the Certifed Novell Instructor community on Linux. Andrew founded theurbanpenguin and has been submitting video training material to his YouTube channel since 2009 and currently has over 8,500 subscribers and 1.6 Million views. Andrew has had two publications with Packt: Citrix Access Gateway VPX Essentials (2012) and Citrix XenApp (2013).

More from the author
More courses by Andrew Mallett
Section Introduction Transcripts
Section Introduction Transcripts

Course Overview
[Autogenerated] Hi, everyone. My name is Andrew Mellott, and welcome to my course. Getting started with Bodman first, just a little bit about me. I'm a little. It's trainer and consultant working on my own company, the open penguin located in the UK This course is designed to give you the skills needed in using and managing containers with Bodman. As you progress through this course, you'll learn how to install and run Portman as a standard user. This is important, as it enables your develops users to manage their own containers without the need of escalating privileges. Some of the major topics that we will cover include installing Portman, creating containers and managing right herbal volumes. By the end of this course, you will be able to fully managed to the container lifecycle and cater for the different needs of your organization, from Web servers to date of a surface. Before beginning this course, you should be familiar with the loons command line and, of course, executing commands. With this knowledge already in your arsenal, you will gain the most from this course on. Really extend your develops capabilities. I hope you'll join me in this journey, learning the details you have always wanted to know about managing containers with Bodman

Managing Writable Data on Persistent Volumes
[Autogenerated] Okay, so we'll be able to find the i d that we need. Let's go through and take a look at configuring are right herbal volume for my SQL. So here we are, back on our command line. And if we take a little bit of care here, we can learn some really important element about Bodman and this is going to do with our user map ings. But first off, we could do something quite easy. Just create a directory. I think we should be up to that. Just goes through and create the directory. My s Q l Now, when we go through And, of course, take a look at this at l s minus L d. We can use escape and Dr bring up the last argument when we take a look at it. We could see then that others only have read and execute on. We relied on the permissions of the user and group tux, so we're not gonna be able to right through to this system. We also need to make sure that we set the correct SC linens context. So we'll do that now. We want to do this now before we start playing around with the ownership. So I'm gonna go through and set this up so we can go through and use our Chikane minus T and we can go through and set it then for our container underscore file underscore t for type and do that for the my SQL directory. So we want to do that before we changed the ownership. Otherwise, we won't be able to use the check on command. No, I'm not able to use the Chown Command to change to the ownership of the file. As an ordinary user, I'm not permitted to change the ownership to somebody. There's no may. So I can't do that. Your own element except if there was a way of becoming route, not forgetting about. So do we want to be able to do this totally is a standard user. But if we remember, we can use pod hman andan share. And if I look at running the I d command, we're running now inside of my own user name space. And it is this is the magic that allow me both to run the containers because I can run them as my own virtual route. But it also means that so long as I'm using the unshared command, I'm working in my own name space, and I can do pretty much what I want within that name space. So let's take a look as I then go through and an unshared on. Then we could go toe and changed the ownership. We want to go to user I d 27 on before then our my SQL directory. Then that's gone through. Nobody started crying. No milk has been spilt. We've moved out and said everything that we need. But how does this actually show to the host itself? When we go back now and list the permissions of my SQL, we could see the ownership has changed to ah 100,000 and 26 Now this is coming from the user i d mapping file on this comes from my own personal space. If I go through and grip for the user tux from within than the D c on sub you I d file we could see the first user. I d user I d one that could be used starts off at the 100,000 mark for tux. So user i d one would be 100,000 which is gonna make user I d 27 the 26th that we see here. So 100,000 and 26 So we've gone through Created the directory we set the SC limits context on We've gone through a made sure that it is right herbal by our user account on we could use the tone command inside of our name space using Portman Unshared. Now we need to test this, don't we?