9 ms·

On macOS brew install podman; podman machine init; podman machine start; podman run ...

by SEJeff 5y ago

cpach 5y ago
Interesting… Will podman automatically create and launch a Linux VM where the containers will live?
- esamatti 5y ago
  Seems like it ------- Podman is a tool for running Linux containers. You can do this from a MacOS desktop as long as you have access to a linux box either running inside of a VM on the host, or available via the network. Podman includes a command, podman machine that automatically manages VM’s. To start the Podman-managed VM: podman machine init podman machine start ------- from: https://podman.io/getting-started/installation https://podman.io/getting-started/installation
  - jhickok 5y ago
    Seems to have some issues creating the temp directories for the VM in an automated fashion (at least with the Homebrew package). But it will work with some tinkering.
b3n4kh 5y ago
It seems like podman machine is deprecated: https://www.redhat.com/sysadmin/replace-docker-podman-macos https://www.redhat.com/sysadmin/replace-docker-podman-macos
- SEJeff 5y ago
  This is from the guy that leads the container team at Redhat: https://twitter.com/rhatdan/status/1433003250991706114?s=21 https://twitter.com/rhatdan/status/1433003250991706114?s=21
  - capableweb 5y ago
    Your comment gave me the impression that Daniel Walsh made some refutation against that podman-machine is being deprecated, but the Tweet you link to say no such thing, unless it's hidden in some sub-tweet (Twitters UX is horrible to discover things). Going straight to the source (https://github.com/boot2podman/machine https://github.com/boot2podman/machine), it says the following: > DEPRECATED (with huge letters) > Podman Machine is now deprecated. Users should try using Vagrant instead. So one can safely assume that podman-machine is in fact getting deprecated.
    - rjzzleep 5y ago
      What you linked to is podman-machine. podman machine is not the same. The former was probably deprecated because podman machine is now part of podman itself. https://github.com/containers/podman/tree/main/cmd/podman/machine https://github.com/containers/podman/tree/main/cmd/podman/ma...
    - SEJeff 5y ago
      I'm not sure if it was you that downvoted me, but you are mistaken. boot2podman/machine, what you linked, is not an official part of podman. It is a third party equivalent and not relevant. The official podman repository is https://github.com/containers/podman https://github.com/containers/podman, and the machine bits are integrated and part of podman proper: https://github.com/containers/podman/tree/main/cmd/podman/machine https://github.com/containers/podman/tree/main/cmd/podman/ma... If it was you that downvoted my comment, please consider not doing that because you disagree. The comment was factually correct and made in good faith. You're equating a third party deprecated podman-machine with the integrated into upstream podman machine. We were not referring to the same thing whatsoever. Hopefully this makes more sense to you now.
      - capableweb 5y 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 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.
- gbraad 5y ago
  Podman-machine was an external project that was derived from minishift and some of the images I made to allow fedora and Podman to be used. This worked, but was mostly a one man project by a community member We have worked with the container team to introduce an actual solution, that also will hopefully soon introduce a new network stack. This we have been testing in CRC for some time. Note: team lead on CRC, previously minisbift. Work closely with the container team. Red Hat employee
  - cpach 5y ago
    There’s so much container innovation going on that I get dizzy just by hearing about it. Lots of interesting projects popping up all over the map.
    - afbjorklund 5y ago
      Then you will be glad to hear that I was planning to continue the podman-machine project, but under a different name... https://boot2podman.github.io/2021/01/24/reboot-new-project.html https://boot2podman.github.io/2021/01/24/reboot-new-project....
      - scns 5y ago
        Was or are? Looks interesting, especially the runs from RAM aspect.
        afbjorklund 5y ago
        It's a "work in progress", basically an updated version of the old projects that serve like a proof-of-concept if you can tolerate the old versions (docker 19.03 and podman 1.9.3) The runs from RAM is an integral part of the project, the new version will have better packaging - using squashfs mounts rather than copying them over to tmpfs like the old one did.
bazzargh 5y ago
hmm, I tried this yesterday, Catalina, fresh install of podman/qemu: ; podman machine start INFO[0000] waiting for clients... INFO[0000] listening tcp://0.0.0.0:7777 INFO[0000] new connection from to /var/folders/tv/ykgkkzr902n062tzjgbtwdc1bgt9y_/T/podman/qemu_podman-machine-default.sock Waiting for VM ... qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2] I hadn't dug into it because the docs for this feature are still missing, and I presumed it hasn't launched - I'd seen it in the demo https://podman.io/community/meeting/notes/2021-04-06/#podman-on-mac-preview https://podman.io/community/meeting/notes/2021-04-06/#podman... So I took a look again: ; vim ~/.config/containers/podman/machine/qemu/podman-machine-default.json # added arguments to cmd, "-cpu", "host" # based on reading https://github.com/GNS3/gns3-server/issues/1639 for that error ; rm /var/folders/tv/ykgkkzr902n062tzjgbtwdc1bgt9y_/T/podman/qemu_podman-machine-default.sock # podman machine start will complain if you don't remove the # socket file after the crash above. `fuser` showed nothing # connected to it ; podman machine start INFO[0000] waiting for clients... INFO[0000] listening tcp://0.0.0.0:7777 INFO[0000] new connection from to /var/folders/tv/ykgkkzr902n062tzjgbtwdc1bgt9y_/T/podman/qemu_podman-machine-default.sock Waiting for VM ... ; podman machine ls NAME VM TYPE CREATED LAST UP podman-machine-default\* qemu 45 seconds ago Currently running ; podman pull alpine Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf) Trying to pull docker.io/library/alpine:latest... Getting image source signatures Copying blob sha256:a0d0a0d46f8b52473982a3c466318f479767577551a53ffc9074c9fa7035982e Copying blob sha256:a0d0a0d46f8b52473982a3c466318f479767577551a53ffc9074c9fa7035982e Copying config sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab Writing manifest to image destination Storing signatures 14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab ; podman run -it alpine sh / # Works!

On macOS brew install podman; podman machine init; podman machine start; podman run ...

by SEJeff 5y ago

On macOS brew install podman; podman machine init; podman machine start; podman run ...

cpach 5y ago

Interesting… Will podman automatically create and launch a Linux VM where the containers will live?

esamatti 5y ago
Seems like it ------- Podman is a tool for running Linux containers. You can do this from a MacOS desktop as long as you have access to a linux box either running inside of a VM on the host, or available via the network. Podman includes a command, podman machine that automatically manages VM’s. To start the Podman-managed VM: podman machine init podman machine start ------- from: https://podman.io/getting-started/installation https://podman.io/getting-started/installation
- jhickok 5y ago
  Seems to have some issues creating the temp directories for the VM in an automated fashion (at least with the Homebrew package). But it will work with some tinkering.

b3n4kh 5y ago

It seems like podman machine is deprecated: https://www.redhat.com/sysadmin/replace-docker-podman-macos https://www.redhat.com/sysadmin/replace-docker-podman-macos

SEJeff 5y ago
This is from the guy that leads the container team at Redhat: https://twitter.com/rhatdan/status/1433003250991706114?s=21 https://twitter.com/rhatdan/status/1433003250991706114?s=21
- capableweb 5y ago
  Your comment gave me the impression that Daniel Walsh made some refutation against that podman-machine is being deprecated, but the Tweet you link to say no such thing, unless it's hidden in some sub-tweet (Twitters UX is horrible to discover things). Going straight to the source (https://github.com/boot2podman/machine https://github.com/boot2podman/machine), it says the following: > DEPRECATED (with huge letters) > Podman Machine is now deprecated. Users should try using Vagrant instead. So one can safely assume that podman-machine is in fact getting deprecated.
  - rjzzleep 5y ago
    What you linked to is podman-machine. podman machine is not the same. The former was probably deprecated because podman machine is now part of podman itself. https://github.com/containers/podman/tree/main/cmd/podman/machine https://github.com/containers/podman/tree/main/cmd/podman/ma...
  - SEJeff 5y ago
    I'm not sure if it was you that downvoted me, but you are mistaken. boot2podman/machine, what you linked, is not an official part of podman. It is a third party equivalent and not relevant. The official podman repository is https://github.com/containers/podman https://github.com/containers/podman, and the machine bits are integrated and part of podman proper: https://github.com/containers/podman/tree/main/cmd/podman/machine https://github.com/containers/podman/tree/main/cmd/podman/ma... If it was you that downvoted my comment, please consider not doing that because you disagree. The comment was factually correct and made in good faith. You're equating a third party deprecated podman-machine with the integrated into upstream podman machine. We were not referring to the same thing whatsoever. Hopefully this makes more sense to you now.
    - capableweb 5y 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 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.
gbraad 5y ago
Podman-machine was an external project that was derived from minishift and some of the images I made to allow fedora and Podman to be used. This worked, but was mostly a one man project by a community member We have worked with the container team to introduce an actual solution, that also will hopefully soon introduce a new network stack. This we have been testing in CRC for some time. Note: team lead on CRC, previously minisbift. Work closely with the container team. Red Hat employee
- cpach 5y ago
  There’s so much container innovation going on that I get dizzy just by hearing about it. Lots of interesting projects popping up all over the map.
  - afbjorklund 5y ago
    Then you will be glad to hear that I was planning to continue the podman-machine project, but under a different name... https://boot2podman.github.io/2021/01/24/reboot-new-project.html https://boot2podman.github.io/2021/01/24/reboot-new-project....
    - scns 5y ago
      Was or are? Looks interesting, especially the runs from RAM aspect.
      - afbjorklund 5y ago
        It's a "work in progress", basically an updated version of the old projects that serve like a proof-of-concept if you can tolerate the old versions (docker 19.03 and podman 1.9.3) The runs from RAM is an integral part of the project, the new version will have better packaging - using squashfs mounts rather than copying them over to tmpfs like the old one did.

bazzargh 5y ago

hmm, I tried this yesterday, Catalina, fresh install of podman/qemu: ; podman machine start INFO[0000] waiting for clients... INFO[0000] listening tcp://0.0.0.0:7777 INFO[0000] new connection from to /var/folders/tv/ykgkkzr902n062tzjgbtwdc1bgt9y_/T/podman/qemu_podman-machine-default.sock Waiting for VM ... qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2] I hadn't dug into it because the docs for this feature are still missing, and I presumed it hasn't launched - I'd seen it in the demo https://podman.io/community/meeting/notes/2021-04-06/#podman-on-mac-preview https://podman.io/community/meeting/notes/2021-04-06/#podman... So I took a look again: ; vim ~/.config/containers/podman/machine/qemu/podman-machine-default.json # added arguments to cmd, "-cpu", "host" # based on reading https://github.com/GNS3/gns3-server/issues/1639 for that error ; rm /var/folders/tv/ykgkkzr902n062tzjgbtwdc1bgt9y_/T/podman/qemu_podman-machine-default.sock # podman machine start will complain if you don't remove the # socket file after the crash above. `fuser` showed nothing # connected to it ; podman machine start INFO[0000] waiting for clients... INFO[0000] listening tcp://0.0.0.0:7777 INFO[0000] new connection from to /var/folders/tv/ykgkkzr902n062tzjgbtwdc1bgt9y_/T/podman/qemu_podman-machine-default.sock Waiting for VM ... ; podman machine ls NAME VM TYPE CREATED LAST UP podman-machine-default\* qemu 45 seconds ago Currently running ; podman pull alpine Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf) Trying to pull docker.io/library/alpine:latest... Getting image source signatures Copying blob sha256:a0d0a0d46f8b52473982a3c466318f479767577551a53ffc9074c9fa7035982e Copying blob sha256:a0d0a0d46f8b52473982a3c466318f479767577551a53ffc9074c9fa7035982e Copying config sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab Writing manifest to image destination Storing signatures 14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab ; podman run -it alpine sh / # Works!