I switched from Docker to Podman since few months, never looked back. Had some headaches to convert some containers but it is very reliable and compatible with kubernetes.
@christianlempa7 ай бұрын
cool, I might try it too :)
@thesuhu6 ай бұрын
What orchestration tool do you use?
@sridharkumar94625 ай бұрын
Do We require to recreate the existing containers from docker to podman while shifting from docker to podman? Or we have something to migrate to those containers?
@TantissTheEmperor5 ай бұрын
@@sridharkumar9462 you can recreate them keeping the config folder.
@mortenaa5 ай бұрын
@@sridharkumar9462Podman 100% supports OCI compatible containers, so if you didn't create your container with something very Docker specific it will conform to the open container format and is then supported by Podman. No migration needed.
@2dorks417 ай бұрын
I've been using Podman for years now. I really appreciate that its user namespaced and doesn't require a daemon to run. Thanks for covering it! Hope to see more tech youtubers dropping "Docker" when talking about containers and just referring to them as containers. Docker's not the only game in town.
@christianlempa7 ай бұрын
Sounds awesome! Yeah, maybe I should do more topics around podman :)
@emptystuff15937 ай бұрын
What's so great about not having a daemon running ? There are hundreds of processes running on your machine at any given time, why bother about one more ?
@loucipher77827 ай бұрын
because they actually only used Docker...
@9SMTM67 ай бұрын
Yes. Well, kindof. The thing is that the term container is a lot more used by other tools too, that are not compatible with Docker like containers (forgot the official name for them).
@TheHeartOfTheEvil6 ай бұрын
@@emptystuff1593 Because if the docker daemon crashes for whatever reason all the containers are going down with it. This is the same reason why updating docker is a pain. Podman doesn't have this type of single point of failure.
@JasonSFuller7 ай бұрын
The big advantage Podman Desktop has over Docker Desktop is the licensing for enterprise use. PD is FOSS (Apache 2.0 license), where DD is only "free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open source projects. Otherwise, it requires a paid subscription for professional use. Paid subscriptions are also required for government entities."
@username77637 ай бұрын
I have nothing against a company trying to make money off of their work, but the fact that it is a subscription-only really rubs me the wrong way. Let me buy a copy that is mine forever and leave me alone.
@haraldfielker46357 ай бұрын
That is a bit of the finger to docker. I love that! Docker went the Oracle route, and tries to charge every corporation user with a docker desktop license. Portman looks super simple and never unterestimate the security aspect.
@_vr7 ай бұрын
Podman is originally developed by Red Hat, and we all know what happened to the Red Hat drama.
@kpaxgo7 ай бұрын
Ups...that was a strong argument to stay away from this project? @@_vr
@FlexibleToast7 ай бұрын
@@_vr that it was overblown and mostly FUD?
@MrTweetyhack7 ай бұрын
and Redhat went the corporate route as well
@bk60106 ай бұрын
@@_vr what drama??
@marcgirard4757 ай бұрын
Switched to Podman 2 years ago now, never looked back! Thanks for the video.
@christianlempa7 ай бұрын
Sounds awesome! :)
@taylom19807 ай бұрын
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. 🙂
@christianlempa6 ай бұрын
Awesome :D
@RobMoerland6 ай бұрын
This is great. It's just eat I need for a project I'm working on. Tnx
@marna_li7 ай бұрын
I used Podman last year at my then-employment. I see a lot of improvements. That is very much welcome. Nice app. A good replacement for Docker Desktop, which is what makes many companies not wanting to use Docker. Podman UI really is cleaner.
@gustavo-santos-dev6 ай бұрын
Honestly, I never thought about changing from Docker to Podman, but this POD creation is really catching my attention, I had some experience building sidecars for containers and is a PITA to test it locally with docker. Awesome content.
@BjrnOttoVasbottenbjovas5 ай бұрын
I wanted to get into containers, but could not risk installing docker desktop on my work pc due to any license consequenses. Really happy with podman! Can do everything i see people doing with docker.
@mrpig22597 ай бұрын
Finally. Been using some of your videos to implement with podman for the reasons you have mentioned. Never have had any issues with podman-compose btw. Keep up the superb work. Cheers.
@pavelperina76296 ай бұрын
Switched in April 23 when I moved to Fedora. Difference is it can be backup-ed and restored from tars and it needs dealing with effective user and group IDs and creating user session during system startup and there are some special commands to move files into and from volumes.
@Trains-With-Shane7 ай бұрын
Think I'll stick with Docker for now but pretty interested especially given the integration of docker-compose types of container deployments. Think i'll spin up a test VM and give Podman a try. Also.. Docker Scout video, Please and thank you!
@kavishgour32677 ай бұрын
Podman-compose is dead. Podman is 100% compatible with docker-compose. Been using it for a while now. Where I work, 95% of our servers are running RHEL. And podman is running in production without any issues. Start by enabling the podman socket: systemctl enable --now podman.socket Then export the following variable to make docker-compose communicate with podman instead of docker(put the export command in .bashrc or whichever shell you're using): export DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock and that's it. You can use your regular compose files as usual with the docker-compose command.
@christianlempa7 ай бұрын
thanks that's good feedback! :)
@alexrosenberg_tube7 ай бұрын
You said 'rootless' and I immediately got confused with the older use of that term from X-Windows. Thanks for the flashback! 🙂
@christianlempa7 ай бұрын
:D
@dee-kryvenko7 ай бұрын
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.
@pndungu12 ай бұрын
I admire what you do Christian. keep it up Lempa
@janjansen62637 ай бұрын
I’m made to switch from docker to Podman about a year ago, I issue have most of the time is a hard coded docker deamon socket in some projects, making a symlink + activating the podman socket will do the trick most of the time. Running podman rootless by default and managing containers as systemd services is a great features
@christianlempa6 ай бұрын
Yep, the systemd feature is nice! I will have a look at it.
@eXsoR657 ай бұрын
This is an excellent video! I’ve also been debating on trying Podman and I think this definitely helped. I will definitely be giving it a try for local container testing.
@christianlempa7 ай бұрын
Glad it was helpful!
@Disi20087 ай бұрын
I like that podman can use quadlets, those are files under /etc/containers/systemd/ that look similar to compose. After systemctl daemon-reload, it will create a system service you can start and will auto start on the next reboot. Podman could always generate system services, but this way it regenerated with the latest systemd version and not onetime.
@christianlempa7 ай бұрын
awesome! didn't know that
@MichaelZimmermann7 ай бұрын
yea these things are awesome. My homeserver is solely based on quadlets(now called podman systemd units).
@Disi20088 күн бұрын
I just had the task to setup gohabor on Ubuntu and this was unstable under Docker (crash of containers after 1-2 days, usually during system updates). Then I noticed Ubuntu does not support the Quadlets of Podman because of the missing systemd-generate tool. You can generate the system services for systemd with catatonit but not from quadlets, at least I couldn't figure it out on 22.04 or 24.04. The tool podlet is really cool and lets you generate quadlet files from docker-compose or running containers. I ended up using Podman-Compose on a slightly adjusted docker-compose.yml file and this runs more stable than under Docker.
@larssamsung30336 ай бұрын
Very focused on Desktop usage on Win and Mac.
@timschannel2476 ай бұрын
Thank you for pointing out this. I am pretty sure it helps the community! Best Regards!
@henderstech7 ай бұрын
Your head looks very smooth. Very nice.
@DaveTaste6 ай бұрын
Gae
@beachfeet60557 ай бұрын
Of course there is always nerdctl as the CLI and Rancher Desk as the GUI. Nerdctl can be run either rootful, or rootless and does more then Podman or Docker as an interface to containerd.
@bluecement6 ай бұрын
Migrating from Docker to Podman is a headache! Especially if you use docker compose!
@FlyRenegade_7 ай бұрын
Great video, thanks, I'm going to try podman tomorrow at work and see how it also fares at building and pushing docker images :)
@christianlempa7 ай бұрын
Thank you so much :)
@Gilgwathir7 ай бұрын
I currently use Podman for all my containers. However, I found one things which is a tremendours headache with Podman: It doesn't play nice with NFS mounts. NFS assumes UIDs are synced between server and client, and the whole subuid things totally flies in the face of that. I just said "screw that" and just mounted my storage using iSCSI... but that comes with a whole set of new problems 😂
@sherwinfrias077 ай бұрын
Exactly the same reason why I'm still using docker.
@cybr7747 ай бұрын
OpenShift would be quite cool to see featured in a video, in particular it's open source version called OKD
@christianlempa7 ай бұрын
I think I still need some time to understand openshift, but it would be nice, yes :D
@FlexibleToast7 ай бұрын
OpenShift is a beast to setup, although it's constantly getting easier. It has a much harder day 1 experience than its competitors, but the day 2 operations of actually getting things deployed is much easier.
@conradtaylor292 ай бұрын
Yes, I would definitely like to learn about Docker Scout.
@bumblingwelshman7 ай бұрын
the biggest upside to podman desktop over docker desktop is it's currently fully opensource and free use both at home and commercially where as docker desktop is no longer free for commercial uses. Where I say currently opensourse about podman given redhats recent actions I wouldn't be surprised if they monetised podman desktop. On a server level though docker is still ahead of podman due to it's swarm mode to allow for scaleable and high available clustering if you didn't want to run a k8s cluster on prem that is (still working on my employer with that 😀).
@christianlempa6 ай бұрын
I'm not so interested in being fully open source or the licensing, TBH :/ The technical bits and pieces are, what makes it interesting for me.
@OleksiiVoronin-hn6qxАй бұрын
I was going to switch to Podman, but then I was overtaken by a compatibility problem with the devcontainer in vscode, which is why the migration plans had to be postponed on my work PC. But among the newer solutions, I’m currently trying finch from AWS, which uses lima, nerdctl internally. I recommend you try it. Thank you for the video.
@be1tube7 ай бұрын
1:47 In keeping with its mascot, PodMan has seal-eye tools. 🥁📀 (I'll show myself out.)
@cmndthor07 ай бұрын
I'm curious about the terminal application you use, is it Mac Exclusive?
@dmi3mis4 ай бұрын
same question.
@user-xl7yp3vh1i2 ай бұрын
4:36 For me lack of proper support of compose files was the only reason which stopped me from using podman some time ago. I don't like imperative docker, i like to use compose files much more, even for simple apps. When i tried podman it still had some issues with some yaml sections about resources limits and so on (don't remember exactly) and also with .override files. But it was few years ago, maybe it's time to give it another chance
@chrisumali98417 ай бұрын
Thanks for the demo and info, have a great day
@christianlempa7 ай бұрын
Thanks! you too :)
@bashardlaleh21107 ай бұрын
one thing I don't much like about your videos is that you always focus on GUIs which is good for local development but not really important for real environments and real work where CLI commands are mostly used, that said, thanks for the introduction about podman I will definitely try it and read more about it.
@christianlempa7 ай бұрын
Really? I always aim to balance GUI with CLI
@bashardlaleh21107 ай бұрын
@@christianlempa IDK but the last 4 notifications I received from your channel were all about GUI, GUI for ansible, GUI for managing containers,.....etc which doesn't pick my interest because I never use GUI for those kins of tasks even om my local laptop, maybe that's just me maybe other people are liking that, just wanted to share my thoughts
@christianlempa7 ай бұрын
@@bashardlaleh2110 thanks! I appreciate your feedback, and you're right. I think GUIs are always nice for beginners and Homelab people, that's why you see a lot of engagement on these videos. But don't worry, it won't become a beginner channel only, I still have some stuff coming up for CLI and terminal lovers :)
@StevePrior2 ай бұрын
I've been using Jenkins running under Docker for a few years with Dind such the build tools (Like Java and Maven) themselves run as Docker containers. I've started using the Kubernetes Jenkins plugin so that those same containerized build tools are now running as Kubernetes pods. Well the problem is that in order to support multi-arch container builds I'm using the Jenkins Docker Pipeline plugin and docker buildx to build the multi-arch images and that seems problematic for running under Kubernetes. So now I'm working on using a containerized install of Podman which I'll be able to invoke as a Jenkins Inbound Agent to be able to do my multi-arch container builds as Kubernetes pods. Once all that is accomplished I'll end up moving Jenkins from Docker to Kubernetes.
@LalitaPaswan-yq6ll7 ай бұрын
Brother's you always provide good content for us thanks for such type of informative content...
@christianlempa7 ай бұрын
thank you so much :)
@calebcrossman94647 ай бұрын
I have one word. QUADLET. I've met the developer of Podman, and have attended a few of his seminars.
@ukrolelo7 ай бұрын
Scout YES!❤
@christianlempa7 ай бұрын
noted :D
@armynyus91237 ай бұрын
using podman exclusively since 3 years. Running rootless just rocks on our prod servers but also locally on my laptop.
@MrCentrax5 ай бұрын
The company I work at recently dropped Docker because of the license issue and it’s been a pain in the ass. I’ll take a look at this
@christianlempa5 ай бұрын
Cool, let me know how it goes
@Artist195 ай бұрын
Pretty cool stuff. I’m currently reading through Podman documentation from Red Hat learning how to use it.
@christianlempa5 ай бұрын
Nice!
@ThatNateGuy6 ай бұрын
I'm still getting first-hand experience with containers. I'd like to learn to be proficient with Podman more than Docker, but I haven't been able to find a single homelab project I'd want to do whose guide for deploying a container was written for Podman, lol.
@huyhandes7 ай бұрын
for mac silicon user, I switched from Docker to Orbstack for better performance since it use rosetta instread on qemu
@kevinnguyen1637 ай бұрын
Docker has an option to use rosetta as well. You just need to enable it in the settings
@stephenreaves32057 ай бұрын
I love podman for using kube files directly instead of docker-compose
@christianlempa7 ай бұрын
That's neat!
@turush45755 ай бұрын
The developer urge to make new, faster, better, safer applications/frameworks instead of helping improving the existing ones
@MaxMustermann-bm7qtАй бұрын
Tried podman a while ago, hated it so much i stopped after 40h. Bad documentation, not everything was supported, problems with setting multiple ports.
@kamiomnik23886 ай бұрын
Great video, now I would like to try Podman XD
@christianlempa6 ай бұрын
You should! :)
@conradtaylor292 ай бұрын
Where can one locate the VSCode extension that you're using to craft a Pod manifest? Love the video and I'll definitely give Podman a go.
@MenkarX7 ай бұрын
AFAIK, docker is also using namespace separation, main vulnerability is misconfiguration or providing excessive privileges for the container. I suppose the same happens in podman as well.
@danielwalsh23637 ай бұрын
One key difference is Podman defaults to rootless with SELinux enabled, Docker defaults to rootful with SELinux disabled.
@MenkarX7 ай бұрын
@@danielwalsh2363 Thanks, will take a closer look at Podman.
@TheJFMR7 ай бұрын
I switched from Docker to Orbstack, some grails tests (from the language groovy) running through a docker desktop it takes 3 minutes and running through orbstack it takes 1 minute
@christianlempa7 ай бұрын
sounds also nice
@mzhomie88806 ай бұрын
Are all problems with devcontainer from VSCode solved? Can you now use podman with devcontainers?
@daniellowry7 ай бұрын
Ive been using podman instead of docker for a while now and its served its purpose excellently. The only annoyance i have wkth it is i csn't just set containers to restart: always and have them come up on the boot of the host. I know i can generate systemd files to do this or use quadlet to make simpler syatemd files but both of those require extra setup whereas under docker I could simply set the restart parameter and the containers would start on boot
@danielwalsh23637 ай бұрын
If you set the restart policy on containers to always, then they should start automatically on boot. You might need to enable the restart services though. /usr/lib/systemd/system/podman-restart.service /usr/lib/systemd/user/podman-restart.service
@daniellowry7 ай бұрын
@@danielwalsh2363 interesting. I had searched for how to do this and the only thing that came up was generating systemd unit files for every container which I didn't really want to do. I didn't know there was a restart service. I will have a look at that, thank you!
@xmagcx17 ай бұрын
the compose is very bad in podman
@tomwilliam2247 ай бұрын
many network issue on windows. 1. port redirct not registered in firewall so the port cannot be accessed from other device 2. cannot access port on parent so it is the best to deploy basic service like redis, mysql etc on podman
@andreas79446 ай бұрын
I need compose files and IDE Integrations. Therefore, docker is still my preferred solution.
@9SMTM67 ай бұрын
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.
@joergsonnenberger68367 ай бұрын
Why timers? A regular systemd unit works just fine to start containers at boot. Been doing that in SuSE's MicroOS for a while, works like a charm.
@Cynyr7 ай бұрын
Was going to say, just use systemd units, or better yet the newer quadlets.
@nio8046 ай бұрын
Unless something has changed recently, allowing access to the docker daemon is equivalent to root access (you can just run a privileged container and do whatever you want as root), so multiple users could just as well run podman with sudo to share images, or use the docker daemon emulation layer that provides a docker socket.
@scheimong6 ай бұрын
Most distros' podman package ships `podman-restart.service`. Enabling it is the easiest and laziest way to get your containers starting on boot. If you want to do it "properly" though, use quadlets. You get all the benefits of a systemd-managed service with it too. Migrating is made easy thanks to the `podlet` project.
@ronm65857 ай бұрын
Thank you.
@christianlempa7 ай бұрын
You're welcome!d
@danielruiz28647 ай бұрын
I made the swich like two years ago, start to use inmutable linux distros and they comes with Podmam by default, using distrobox also has been a game changer for me. About the Portainer and Podman Desktop thinks, i really dont use any of them
@BogdanSerban7 ай бұрын
I don't understand why podman desktop isn't available as a webui like portainer
@kavishgour32677 ай бұрын
Podman is rhel product. Cockpit has full support for podman.
@epicmap6 ай бұрын
13:15 are you having earthquake? :) Good video btw, thank you. That pod k8s functionality is what really made me consider trying podman.
@christianlempa6 ай бұрын
lol, no it's because the camera is mounted to the desk, which is not ideal :D
@RohithRPai7 ай бұрын
I personally use Rancher desktop which also supports Kubernetes.
@christianlempa6 ай бұрын
looks interesting, also
@kamillatocha2 ай бұрын
but how do i seach for images in podman like i do in docker desktop .......
@Grimm_Holt6 ай бұрын
What do you use to theme your terminal? I would love to achieve something similar on Linux. The separators between commands really work well with my brain.
@rashshawn7796 ай бұрын
Podman binary seems to be updated only for redhat distribution. Other distro the version is quite old. Latest version of podman is 4.9 as of today.
@batemanjo94 ай бұрын
openSUSE stays on top with their package updates. The current version as of today is the latest Podman stable release 5.0.1
@hendrjl7 ай бұрын
Hi Christian, thanks for great explanation. but, may i know how and what is the configuration of your terminal so the result are displayed on the bottom while the input is still in the top ? thanks
@christianlempa7 ай бұрын
Warp
@insu_na7 ай бұрын
I've been using podman for distrobox
@andreasantinato10597 ай бұрын
A very interesting argument, I will look up to podman in the near future. Another question: what terminal are you currently using?
@christianlempa7 ай бұрын
It's warp terminal
@phanta5m6 ай бұрын
many dev tools still prefer docker and just not work in podman, so i save the headache since to just using docker
@kebab-case7 ай бұрын
My experience with Podman isn't as good as with Docker. I feel like Podman is not fully finished, I have experienced some bugs with it.
@VaibhavShewale7 ай бұрын
so i should start learning podman as well?
@manofwar93075 ай бұрын
I've been interested in the security benefits of podman for a little while now, but I'm a bit worried about potential issues when trying to use podman to run a reverse proxy since you often see issues when you don't open ports 80 and 443 for them. I'd be curious to see a successful implementation of traefik in podman
@timocov5 ай бұрын
Unfortunately podman compose isn’t a replacement for docker compose and apparently not well maintained :( yes, it might support very very basic use cases, but if you have more than few lines of code in compose file most likely something won’t work (and good for you if you notice that because of an error, not silently ignoring fields from a file)
@Jikdor7 ай бұрын
Running a buch of docker containers on my servers, diden't hear about Podman before, gling to try it out.
@jenialherdianto292Күн бұрын
i wonder why no one uses podman for supabase
@HendersonHood6 ай бұрын
Unfortunately does of us who manage thousands of docker container applications cannot simply abandon docker when a new challenger comes along: and there will be many appearing in the next decade.
@Puddyglum6 ай бұрын
Try compatibility mode in Podman Desktop. Most of my docker commands and tools still work fine.
@Stormface167 ай бұрын
If you run single containers as services - Podman is great. If you spin up applications as integrated services there is no better solution than docker compose
@daniellowry7 ай бұрын
You can run docker-compose files in podman. I've been able to deploy stacks from portainer with podman. The compose files were originally designed for docker and most of them required no changes. The only change I had to make to some of them was point it at the podman sock instead of the docker sock
@LondonGlen6 ай бұрын
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```
@christianlempa6 ай бұрын
that's a nice trick! thanks for sharing :)
@looper61207 ай бұрын
Looking forward to a new series of Kubernetes video!!
@zd26007 ай бұрын
Yes, Docker Scout for SBOM please !!
@mohdhakimi537 ай бұрын
I have a question about what security priority is appropriate for Linux vs Windows vs Mac OS
@tcurdt7 ай бұрын
I would love to switch but podman networking still has some major issues - for me at least.
@danielwalsh23637 ай бұрын
Please report these flaws? Have you tried Podman with the netavark back end?
@tcurdt7 ай бұрын
@@danielwalsh2363The ticket(s) are open - they just don't seem considered high priority.
@tcurdt7 ай бұрын
@@danielwalsh2363 netavark sounds interesting. You have experience with it? Would you run it in production?
@hanes27 ай бұрын
Been using pod man in prod since 2020.
@tonychia22276 ай бұрын
I am on Mac OSX Sonoma with M1
@christianlempa6 ай бұрын
cool!
@darknetworld7 ай бұрын
It all come down to user choose or they can try two way while working on their projects. It nice to expand some skills.
@christianlempa6 ай бұрын
true
@kopparsulfat7 ай бұрын
Good video as usual. 👌
@christianlempa7 ай бұрын
Appreciate that
@kawantrindade24597 ай бұрын
Do a video about Jobs, Cron Jobs, Daily Schedules the best softwares to use in a homelab with web panels
@christianlempa6 ай бұрын
Good idea, let's find a way it's gonna be attracting to people on YT :D
@thespencerowen7 ай бұрын
Podman doesn’t work with the :Z option on OSX which makes it incompatible with Ansible-navigator There is a known issue that won’t be fixed. If you need Ansible on OSX then you need docker not podman
@danielwalsh23637 ай бұрын
Docker must have SELinux disabled, you can disable SELinux separation for Podman as well, so you can use it. Please point to the issue you are talking about not working on OSX?
@bk60106 ай бұрын
Remember to keep SELinux enabled
@christianlempa6 ай бұрын
👍
@imetvnj7 ай бұрын
Yes bring on scout
@christianlempa7 ай бұрын
good idea :D
@Rakstawr5 ай бұрын
Podman is hard on mac silicon. Barely ever runs and certain containers are impossible
@szymex227 ай бұрын
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
@christianlempa6 ай бұрын
interesting!
@WillBelden3 ай бұрын
Hmmmm. Lack of "compose" style files... that might be a deal killer for me.
@ruixue69553 ай бұрын
Can podman use the Docker Images in The Docker hub?
@stefangranath38417 ай бұрын
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?
@mysystem327 ай бұрын
Struggled with podman networking vs docker. Docker simple to create a private bridge network that a few containers connect to. Podman pod networks expose all listening ports to public.
@danielwalsh23637 ай бұрын
Did you open an issue on this? This could be a difference between rootless and rootful, Docker runs rootful by default and Podman rootless. You are more limited in networking in rootless mode.
@hoang-himself6 ай бұрын
The only thing preventing me from migrating to Podman is incompatibility with dev containers features.
@AliCaliskan-km5jc7 ай бұрын
Docker scout, for sure!!!!
@christianlempa7 ай бұрын
awesome, put it on my list :D
@cheebadigga40927 ай бұрын
you can also alias docker to podman so you don't even have to remember to type podman
@christianlempa7 ай бұрын
I'm not a big fan of this, but sure, it's also possible :)
@srikantas24607 ай бұрын
I love the video , I'm trying to use docker in freebsd but it is not officially supported and podman fits well for me can you please make a video on how to migrate docker container to podman it would be really helpful to actually consider giving it a shot.
@christianlempa7 ай бұрын
Thank you! :)
@elalemanpaisa7 ай бұрын
But you can use kubernets yamls instead for docker compose files and podman does not run as root by default!