Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Podman Desktop celebrates 3M downloads

podman-desktop.io

Post reply on HN
Print view View original

71–80 of 82 posts

Re: Podman Desktop celebrates 3M downloads

#71

Post by nozzlegear »

hdjrudni wrote: post #31
seemaze wrote: post #9

Earlier quoted context omitted.

It supports Kubernetes *.yaml manifests?

Is that a question or a statement? I'm running Kubernetes on Docker Desktop. But every few months Docker Desktop either outright craps out and forces me to wipe everything and rebuild my containers or the latest annoyance is that it keeps giving me popups saying something something couldn't start Ubuntu.... but then seems to work perfectly fine after skipping it 10 times.

Podman directly supports kubernetes manifest files without running a kubernetes instance. You can do:

    podman kube play --replace k8s.yaml
    podman kube down k8s.yaml
    podman kube apply --namespace project -f k8s.yaml
I'm not familiar with Docker Desktop so maybe that just works there too.

Re: Podman Desktop celebrates 3M downloads

#72

Post by shykes »

kstrauser wrote: post #64
shykes wrote: post #38

Earlier quoted context omitted.

Hi, I'm the founder of Docker. The decision to launch Docker Desktop, and deprecate Docker Machine, had nothing to do with revenue. Desktop was free when we launched it in 2016, and it remained free until 2021. By then Docker had a new CEO, a new board, and I was gone. So the two events (launch and monetization) could not be more disconnected. The reason we launched Docker Desktop (initially known as "Docker for Mac"…

I do so wish we could have those features without needed a desktop app for them. There’s never a case where I’d want to run Docker Desktop for anything GUI.

You can't get around packaging it as a desktop app - that's how you get the seamless "drag into Applications folder, double-click" install experience. I agree you don't necessarily need a full-blown desktop GUI. The original version shipped with the whale menu bar icon, a basic settings page, and that's it.

I do think it makes sense to add more GUI features over time, to make Docker more approachable - not everyone is a CLI wizard. But, it shouldn't make the app slower or annoying to use for those who don't need it.

Re: Podman Desktop celebrates 3M downloads

#73

Post by user3939382 »

travisgriggs wrote: post #62
user3939382 wrote: post #54

After hearing about it for years I finally said ok sure I’ll try it. Swapped it out. CPU went to 100%. kill -9. Maybe next year. I don’t have time unfortunately to unravel stuff like this, it has to just work.

My experience was exact opposite. $ brew install podman-desktop … play a little … $ brew remove —zap docker-desktop Have been happy ever since. No more smells of enshittification. Now if I could just zap slack and figma…

I used matterbridge to bridge local ircd to Slack and a bot to do a 2 way sync. Now people are free to use slack but I don’t have to look at it, and I can freely integrate my tools etc without Slack’s bullshit and easily move/integrate/point it somewhere else down the line.

Figma is so slow on my 3-4 year old x64 mbp I couldn’t possibly use it.

Re: Podman Desktop celebrates 3M downloads

#74

Post by foresto »

bootsmann wrote: post #43
foresto wrote: post #29

Earlier quoted context omitted.

I run rootless containers on a low-power system. With Docker, I found rootless setup to be a PITA, despite having experience with unprivileged LXC containers. The manager daemon constantly consumed system resources even when no containers were running. Docker upgrades sometimes refused to run my containers until I chased down whatever storage driver problem they introduced in the latest version. When the most recent…

> Even the little cron script I wrote to query Docker for pending image updates just worked with Podman tools Podman comes with an auto-update flag you can set for containers that uses systemd to do this for you. Takes a bit of reading to get it right but its smooth sailing mostly.

Good to know, but my script is for a different workflow: It checks for updates to remote dependencies of my running custom containers. (For example, when alpine:latest points to something new.) It then prints a message for cron to email to me, noting that it's time to rebuild my custom stuff.

Re: Podman Desktop celebrates 3M downloads

#75

Post by jcotton42 »

OptionOfT wrote: post #61
osigurdson wrote: post #11

I'm glad they have podman desktop. Personally though, once I realized that I can use the command line version without it (unlike docker in my experience) I uninstalled it as I don't really need the UI / KIND, etc. For me the command line is fine and having something where I don't have to first shell into wsl is great (it just runs it itself behind the scenes). Of course, Linux is generally better for development imo…

I prefer to use podman/docker/rancher on windows because then the VM runs on HyperV. Whereas when I install Docker in WSL it runs inside of my WSL VM.

These days Docker Desktop on Windows uses WSL as its backend by default.

Re: Podman Desktop celebrates 3M downloads

#76

Post by osigurdson »

electroly wrote: post #67
osigurdson wrote: post #57

Earlier quoted context omitted.

In my experience, Docker Desktop was needed in order to use the CLI in Windows. It seemed fairly heavyweight as well. Maybe that has all changed now, not sure. In any case with podman on Windows, no UI is needed and you don't have to shell into WSL to use it.

You can run the regular Docker engine inside WSL2 and run the regular Docker client on Windows with DOCKER_HOST set. This has been true since 2016 when we originally got WSL2, with the exception that we used to have to enable systemd (but no longer do).

Good to know. What are the steps to get this working assuming you already have WSL enabled on your machine, but don't have any distros yet?

Re: Podman Desktop celebrates 3M downloads

#77

Post by osigurdson »

CaptainOfCoit wrote: post #65
osigurdson wrote: post #59

Earlier quoted context omitted.

Yes. For some the distinction between the two is almost nothing as WSL is pretty seamless. However, using Podman directly in your normal Windows shell opens up more use cases. Podman is of course running everything behind the scenes using WSL.

> For some the distinction between the two is almost nothing as WSL is pretty seamless WSL1 yes, but not WSL2, which the parent explicitly mentioned. WSL2 is just virtualization with a fancier name, might as well use VirtualBox and similar at that point.

While it is fundamentally a VM, it is far more seamless than running a regular VirtualBox.

Re: Podman Desktop celebrates 3M downloads

#78

Post by electroly »

osigurdson wrote: post #76
electroly wrote: post #67

Earlier quoted context omitted.

You can run the regular Docker engine inside WSL2 and run the regular Docker client on Windows with DOCKER_HOST set. This has been true since 2016 when we originally got WSL2, with the exception that we used to have to enable systemd (but no longer do).

Good to know. What are the steps to get this working assuming you already have WSL enabled on your machine, but don't have any distros yet?

It should be along these lines:

- Install Ubuntu distro in WSL2.

- Create an ssh key pair on the Windows side using ssh-keygen.

In Ubuntu:

- Install Docker engine using Docker's apt-get instructions for Ubuntu.

- Add the ssh public key to ~/.ssh/authorized_keys.

In Windows:

- Run "wsl hostname -I" to get your WSL2 hostname.

- Test "ssh user@wsl-host", using the WSL2 hostname. It should work without prompting for a password.

- Unzip docker.exe somewhere.

- In your user environment variables, set PATH to include the directory with docker.exe, and set DOCKER_HOST to "ssh://user@wsl-host", using the WSL2 hostname.

That should be it; you should now be able to run docker normally from your Windows user, using file context from the Windows side.

Re: Podman Desktop celebrates 3M downloads

#79

Post by osigurdson »

electroly wrote: post #78
osigurdson wrote: post #76

Earlier quoted context omitted.

Good to know. What are the steps to get this working assuming you already have WSL enabled on your machine, but don't have any distros yet?

It should be along these lines: - Install Ubuntu distro in WSL2. - Create an ssh key pair on the Windows side using ssh-keygen. In Ubuntu: - Install Docker engine using Docker's apt-get instructions for Ubuntu. - Add the ssh public key to ~/.ssh/authorized_keys. In Windows: - Run "wsl hostname -I" to get your WSL2 hostname. - Test "ssh user@wsl-host", using the WSL2 hostname. It should work without prompting for a pa…

Thanks for the information. I think for some use cases this is perfectly fine but for others, a kind of one-stop-shopping approach is nice as well. For instance with podman (not desktop, just the cli), you only have to run: "winget install -e --id RedHat.Podman" and you are good to go. This is nice, particularly on bigger teams when you want to reduce friction to a bare minimum.
Post reply on HN