Комментарии:
I swithced to podman due to docker licensee. As i understand i can use it for now for free
ОтветитьPardon my ignorance, but what is the terminal app, shell, or config doing the isolated input and output 'frames'? And the gravy that is the IDE-like browsing of the command history.
ОтветитьAre all images 100% compatible between docker and podman?
ОтветитьMigrating from Docker to Podman is a headache! Especially if you use docker compose!
ОтветитьAnyone else notice their mascot is very similar to dugtrio?
Ответитьmany dev tools still prefer docker and just not work in podman, so i save the headache since to just using docker
Ответитьyou can use docker-compose with podman-service by defining DOCKER_HOST env variable
systemctl --user start podman.socket
export DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock
No, it's time to switch to k8s 😜
ОтветитьHi Christian! You have a very useful video explaining Wireguard configuring. What about the same video with Shadowsocks-libev tutorial? It will be great! Thanks for your job!
ОтветитьNice video! Realy made me doubt now. Maby i'll run it beside docker te test fisrst,
Docker is stil a bit difficult
Especially bindmount propagation. Can you do a indept video about that?
What the heck is docker skout. sounds like a nice addition!
Again thanks for sharing :)
warp ? a good termianl ~
ОтветитьMan, there is so much water in this video:(
ОтветитьDocker desktop is a joke on Linux, because it similarly running qemu that eats up tons of RAM.
ОтветитьClicked on that video because expected alternative for docker compose workflow..
Got something about desktop and graphical interface(wtf?!) and info that compose isn't really a thing!
So this thing is not an alternative at all.
I have been in IT for over 25 years and have no idea what docker or podman is. I have no idea what a container is, nor if i will ever have a use for them. From what i gather, they are VMs but instead of a full OS, its just a single app? I dont get it. Also everytime i try to deploy anyting fun, like a pihole or TruNas, i get bored and wonder why people spend thousands of dollars playing with networking as a hobby.
ОтветитьGood video.
ОтветитьGreat video, now I would like to try Podman XD
ОтветитьI still need Docker 😢. I tried podman then use some image of bitnami, then I have to change ownership but podman cannot resolve as Docker, I always get permission denied :”(
ОтветитьI hope my IT team doesn't see this video. I have to thoroughly abuse docker's security concerns to keep out systems running.
ОтветитьIf you want to use a port lower that 1024 without running as root, then you can redirect traffic from a one port to another via a firewall rule.
Here is the example for iptables.
```sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 21 -j REDIRECT --to-port 2121```
I need compose files and IDE Integrations. Therefore, docker is still my preferred solution.
ОтветитьHi there, this is a very good video for me. Help me to understand a lot about docker and podman. But I am very curious about the screensaver on your Mac. Could you tell us how to get one of that?
ОтветитьLearn docker to use podman in production
Ответитьthe best thing for me about podman is that I am able to manage my containers/pods using systemd thanks to quadlet
It adds a very nice integration to linux and keeps everything under the same logic
Video on Docker Scout please
ОтветитьBut you can use kubernets yamls instead for docker compose files and podman does not run as root by default!
ОтветитьI personally use Rancher desktop which also supports Kubernetes.
ОтветитьPodman is a Dugtrio and Docker is a Diglet :)
ОтветитьInteresting argument!
Little curiosity: were we can get that awesome Matrix animated wallpaper?
I did the reverse, I was using podman for a year or so but really never got into the advanced features due to having to fight with SELinux and stuff like that to get various software running and it was rootful anyway.
I know docker is a little bit less secure, though is there really a difference when comparing both used in root mode?
At the end of the day, a docker installation is just easier to maintain when there is a much bigger community around it
I don't see value in this video. You spend so much time showibghe UI and commands that are exactly the same as docker but barely said why we should ever care bout this thing
Ответитьsimple Answer: Podman and Buildah are OSS. So you should use Podman...
Ответитьwell why not, use them both
ОтветитьHearing "poTman" over and over again, it's just too funny. It is "poDman", with a D
ОтветитьCan I just easily use the Nextcloud docker image with Podman?
Ответитьso i should start learning podman as well?
ОтветитьUsing containers in a desktop app seems weird to me. It kills the beauty of docker: One line / a docker-compose.yaml and it works. Downloading an extra app and klicking around..
ОтветитьWith docker desktop I need to be logged in to run my containers in Windows. With podman will it run more like service so I can reboot and expect pods to run straight away?
ОтветитьIt’s a great fit with example at work we use Ngnix Proxy Manger with podman on Rocky Linux.
ОтветитьBeen using pod man in prod since 2020.
ОтветитьIsn't the licencing also different? Especially when working in a professional setting? If so, that is a very important omission from this video. Secondly, you use a web-application with a DB as an example for a pod. This is extremely bad practice as you must always consider the control plane to move pods around and/or auto-scaling. With scaling alone, you will have a copy of the DB in each replica which is certainly not what you want. I would strongly suggest to add a note about this lest you give people dangerous ideas that they will only realise when it's too late.
ОтветитьIt all come down to user choose or they can try two way while working on their projects. It nice to expand some skills.
ОтветитьI’ve started to play around with Podman just to see what it’s like. I recently discovered that you can generate a Kubernetes v1 yaml file from an existing Podman pod or container. This is good because I can run my existing docker compose files on Podman to create the containers. I then use “podman kube generate” to build a Kubernetes yaml file from my existing container setup. Maybe my method is not very practical but to me it’s still pretty cool. 🙂
ОтветитьPodman being daemonless can make some things more annoying.
You will have to create either cronjobs or systemd-timers to automatically start containers at boot, which Docker will do.
Also the Docker daemon is shared between users (which is probably why it's such a pain to do Docker rootless, though Docker can also do rootless containers AFAIK), Podman doesn't have such a synchronization.
This means, that every user will have to download or build their images anew, so if you switch between root (sudo) and your user, you may have to rebuild images more often than you thought.
And of course there's the gotchas you mentioned with ports etc, which can also make it painful to follow guides. I've also seen some subtle differences in how Podman build and Docker build interpret Docker images (such as the copy command, I beliefe the difference was how they treat directories with or without a following slash). Usually not to hard to work around, but difficult to spot, and can make it annoying if you want to distribute a containerfile to others that may have another engine, and are not super familiar with containers.
I didn't finish the video and I have already uninstalled docker! Let's see how this goes
Ответитьyou may like cockpit also
ОтветитьGuys, I will save you some time. Why Podman is better than docker and why you should switch:
1. Podman is Rootless (it is harder to break the system)
2. Podman has pods like in k8s so yoou can run pods in 1 container (the same shit as docker compose actually)
So in my understanding Podman is the same, and if you use docker for local dev then you have no reason to switch
Podman is backed by Red Hat, and it also is known to step away from Kubernetes standards. Rancher Desktop is light years ahead, they support containerd instead of docker to be in line with Kubernetes baseline, it based on k3s/k3d, and somehow I trust SUSE more. And yes, it can also be a drop in replacement, and not just by way of mimicking Docker but actually using Docker CE with k3d instead of containerd/k3s for these who just develop apps and don’t care about 1:1 matching environment to real Kubernetes. And it comes with Compose and other plugins, yes.
Ответить