(Points and laughs at Nate) Hey, don’t blame me, just following Scott! 😄 Thank you so much gents! This is a great video for me to point new podman users towards to give them a simple starting point. 👍
Support for the newer features in Podman like quadlets, and the older version of systemd in RHEL8 means to get the best experience from Podman you need to be on recent versions of RHEL9
podman run is for instantiating a *NEW* container instance. It looks at the container repositories for the name you've referenced in your podman run command and then will make a new container from that image. podman start is for running already existing container instances. When a container is killed or exits, it will still exist, it's just not running. podman start will take a specific container instance's name or Container ID and will start it running again. To put it another way, podman run creates a copy of a container from an image and runs a new instance of it. podman start will take an existing container instance that is stopped or exited and resume running it. It's important to note that you could see this for yourself by using the commands in different situations. If you use podman start when you really need podman run, it will produce an error. If you use podman run when you really need podman start, it'll start asking about what repository to find the image as you probably don't have an image named floof_hooligan (or whatever the container instance name is). Try it at this lab: www.redhat.com/en/interactive-labs/deploy-containers-podman-container-tools See for yourself what happens when you take a podman run command and instead use start, or visa-versa.
Unless you are building from source, podman is difficult to get started with latest version. The package version from distros are quite far from latest. Imagine looking at a podman 5.0 tutorial but your distro gave you 4.3 or something. It is quite annoying. Second, podman desktop works only on fedora I think, there doesn't seem to be any configuration for you to change the distro. (last I tried on wsl)
The content we covered in the show has worked in Podman for a while, so you shouldn't need Podman 5 to find success. That said, Podman 5 is available on RHEL9.4 as well as Fedora. Ubuntu 24.04 uses 4.9.3. So maybe this is a distro choice? RHEL does pretty well at keeping updated stuff while the releases are in "Full Support" lifecycle phase, which right now is RHEL9. RHEL8 just went to "Maintenance Support" so it should largely stop getting updates except for Critical and Important security errata. I use Podman Desktop on my Mac, so it's not just Fedora; though I've not looked at whether or not it's available (and works well) on Windows.
But why, when you can replace Docker with Podman? And, in fact, install the podman-docker utility so you can even run 'docker' commands (which will keep your automation tooling intact or provide a 'compatibility layer' for people with long command memories).
The hands on labs are super cool. Kudos Red Hat.
(Points and laughs at Nate)
Hey, don’t blame me, just following Scott! 😄
Thank you so much gents! This is a great video for me to point new podman users towards to give them a simple starting point. 👍
Support for the newer features in Podman like quadlets, and the older version of systemd in RHEL8 means to get the best experience from Podman you need to be on recent versions of RHEL9
Can you please explain the difference between podman run and podman start? Thank you kindly.
podman run is for instantiating a *NEW* container instance. It looks at the container repositories for the name you've referenced in your podman run command and then will make a new container from that image.
podman start is for running already existing container instances. When a container is killed or exits, it will still exist, it's just not running. podman start will take a specific container instance's name or Container ID and will start it running again.
To put it another way, podman run creates a copy of a container from an image and runs a new instance of it. podman start will take an existing container instance that is stopped or exited and resume running it.
It's important to note that you could see this for yourself by using the commands in different situations. If you use podman start when you really need podman run, it will produce an error. If you use podman run when you really need podman start, it'll start asking about what repository to find the image as you probably don't have an image named floof_hooligan (or whatever the container instance name is). Try it at this lab: www.redhat.com/en/interactive-labs/deploy-containers-podman-container-tools See for yourself what happens when you take a podman run command and instead use start, or visa-versa.
Does this podman name inspired from K8s actually😅?
Unless you are building from source, podman is difficult to get started with latest version. The package version from distros are quite far from latest.
Imagine looking at a podman 5.0 tutorial but your distro gave you 4.3 or something. It is quite annoying.
Second, podman desktop works only on fedora I think, there doesn't seem to be any configuration for you to change the distro. (last I tried on wsl)
The content we covered in the show has worked in Podman for a while, so you shouldn't need Podman 5 to find success. That said, Podman 5 is available on RHEL9.4 as well as Fedora. Ubuntu 24.04 uses 4.9.3. So maybe this is a distro choice? RHEL does pretty well at keeping updated stuff while the releases are in "Full Support" lifecycle phase, which right now is RHEL9. RHEL8 just went to "Maintenance Support" so it should largely stop getting updates except for Critical and Important security errata.
I use Podman Desktop on my Mac, so it's not just Fedora; though I've not looked at whether or not it's available (and works well) on Windows.
Can you do an episode about docker ?
But why, when you can replace Docker with Podman? And, in fact, install the podman-docker utility so you can even run 'docker' commands (which will keep your automation tooling intact or provide a 'compatibility layer' for people with long command memories).
@@scottmcbrien6535 ok, will play with it at home
@@scottmcbrien6535 what about docker compose?
Check out Nate's explanation @28:30!
@@RedHatEnterpriseLinux is this real??????????
It already has 😊