Hacker News new | ask | show | jobs
by capableweb 1756 days ago
Thanks for clarifying! My mistake in confusing the two, hopefully one can understand how another can make the mistake though as one is named "podman machine" and the other "podman machine".

My main issue with your comment (https://news.ycombinator.com/item?id=28391265) still stands, you're linking a third-party source with the impression that that source said it's in fact not being deprecated, when there is no such text in that source.

I did not downvote you, but I can absolutely understand why someone would do that, since the tweet seemingly has nothing to do with the comment your original comment was replying to.

For what it's worth, complaining about downvotes is almost never worth it. Makes for boring reading and the people downvoting you won't read it anyways.

5 comments

I'm saying the source is saying this is what to use, which was confirmed by reading the source and seeing the "deprecated" version was not even related to the project whatsoever.

Dan is the guy that has been with the docker project through the redhat fork and to the creation of podman from the very beginning. If he says podman machine is what to use, it is not deprecated. Have you ever listened to Dan speak? He's very pragmatic about these things.

Being one of the authoritative decision makers, if he says to use it, it is not deprecated. A literal 1 minute perusal of the podman upstream source confirmed.

> since the tweet seemingly has nothing to do with the comment your original comment was replying to

Saying the lead developer is recommending using machine right after someone claims it’s deprecated seems relevant?

The comments were regarding two different projects, one is deprecated (old podman-machine) one is not (new podman machine)
It's also in the documentation https://podman.io/getting-started/installation
I added some clarification (hopefully) to the README, it gets a bit confusing when terms like "Machine" and "CoreOS" get reused
next your going to be complaining that its too easy to confuse docker-compose with docker compose :P