Podman vs. Docker 

Kubernetes is deprecating Docker as a container runtime after v1.20.

​@@janusz1697You do not need to panic. It’s not as dramatic as it sounds. TL;DR Docker as an underlying runtime is being deprecated in favor of runtimes that use the Container Runtime Interface (CRI) created for Kubernetes. Docker-produced images will continue to work in your cluster with all runtimes, as they always have.

Not many people used Docker swarm now whether docker or podman kubernetes has become the industry standard

They have bought Red Had

See ibm.biz/write-backwards

It is done with a lighted board and neon markers. The camera is 180-degree phase shifted, i.e. mirror image.

It imitates the docker interface. You can alias it to docker and forget about it

Podman compose only exists to allow compatibility with Docker. It's not part of the normal workflow. Pods make it unnecessary. You manage them the same way you manage simple images, just adding '--pod' to the command mainly. Podman simplifies everything.

@@biscotty6669 you just called the whole concept of compose files unnecessary. It's far from it.

Podman has the ability to manage networks, with the same commands as Docker. podman network ... Rootless containers are more limited, because of some constaints of the Linux kernel on rootless users, but with pasta network service, you can get to most controls.

tons of free time, plenty of motivation, reading documentation or videos whichever works better for you and most importantly practice

Hello John! Sorry for the late reply, but like Flesz said, lots of free time 😅 with the popularity of containers and microservices, I’d recommend a certification from The Linux Foundation, specifically the CKAD, Certified Kubernetes Application Developer, to get started. There’s various ways to study (free and not-free), but it’s a great way to start learning and get a lot of hands-on experience!

if you believe that podman can do its magic, its easy to believe that computer technology allows to flip image vertically

Since Podman can go away when a container is running, and does so any time you daemonize a container (podman run -d ...) Then Podman does not use any CPU/RAM or Network when containers are in steady state. Usually people leave Docker daemon as well as containerd running, so it uses CPU and RAM when the system is just running containers. As far as containers are concerned you should see no difference between a running Podman container or Docker container.

Hi, I'm also from Poland

☺

🙌

Runs smoothly! Does not task your system whatsoever!

Yea podman uses the same docker compose file.

Yes, podman images are fully compatible with docker.

I saw his face and thought that as well, i guess everyone has a non related relative somewhere in the world

In English the 'right' way to pronounce a word is simply the way people pronounce the word. When enough people start saying a word differently it makes it into dictionaries (like the alternate pronunciation of daemon has). Many native English speakers say daymen or deh-mon... you say tomayto I say tomahto ...

Kubernetes uses Container Runtime Interface (CRI). The idea behind all with Podman is to split the codebase in multiple projects (vs monolithic Docker approach) for specific purposes and the CRI implementation is project CRI-O, so Kubernetes uses CRI-O. Kubernetes used docker-shim in the past but that has been deprecated as non standard. Today it uses containerd IIRC. Podman makes easier deploying to Kubernetes, but Kubernetes itself runs containers with CRI interface so one possible option is CRI-O. Both Podman and CRI-O use runc/crun to talk to the Linux kernel in order to run containers. Hope it helps clarifying!

Podman supports running kubernetes YAML file natively using podman kube play. This makes it easy to take kubernetes workloads and launch them on your host machine without requiring kubernetes at all. Similarly Podman can generate kubernetes.YAML files directly from locally running containers and Pods using podman kube generate. Finally podman kube deploy can actually take locally running containers and pods and launch them directly into a kubernetes cluster. Specicially kubernetes (kubectl) does not interact directly with Podman, but uses CRI-O which is a daemon based on the same underlying libraries and storage as Podman.