Hello Guys, Is this a valid approach for running Podman in MacOS ? https://developers.redhat.com/blog/2020/02/12/podman-for-macos-sort-of/ It seems similar to Docker Machine, and it works well for me. Any thoughts? Regards, Ezequiel
On 2/13/20 12:44 PM, Ezequiel Aguilar wrote:
Hello Guys, Is this a valid approach for running Podman in MacOS ? https://developers.redhat.com/blog/2020/02/12/podman-for-macos-sort-of/
It seems similar to Docker Machine, and it works well for me.
Any thoughts?
Regards, Ezequiel
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Yes, This works.
Ezequiel Aguilar wrote:
Is this a valid approach for running Podman in MacOS ? https://developers.redhat.com/blog/2020/02/12/podman-for-macos-sort-of/
It should be, the intention is to provide a "Podman Toolbox"... Not everyone likes VirtualBox, but QEMU support is also included. It is possible to make it accelerated on the Mac, similar to KVM: https://github.com/boot2podman/machine/issues/5#issuecomment-548442359 Both VirtualBox and QEMU should work on all the three platforms. There is still some work to do, with the other 3 "machine" drivers. And work is under way, to upgrade Tiny Core and to upgrade Fedora: * Tiny Core Linux 11.0 * Fedora 31
It seems similar to Docker Machine, and it works well for me.
Any thoughts?
Glad you like it! It's not really a native "Podman for Mac", but should be a start... Like the article says, you can also run the full CRC on the Mac: https://developers.redhat.com/blog/2019/09/05/red-hat-openshift-4-on-your-la... That will give you a more integrated product (i.e. no VirtualBox) It also requires a _lot_ more resources from your laptop, though. Recently we are also added Podman support to Minikube, for v1.8.0. This means that we have "podman-machine" and "minikube podman-env", which should be comparable to "docker-machine" and "docker-env" ? You will get some basic Kubernetes support, also with Boot2Podman. /Anders PS. You can follow developer blog at https://boot2podman.github.io/ There will be some kind of hackathon, before foss-north conference. PPS. There were more stuff in Docker for Mac and in Docker Desktop: * https://www.docker.com/blog/docker-for-mac-windows-beta/ * https://www.docker.com/blog/get-to-know-docker-desktop/ I was just doing a Boot2Podman ISO, and then ported machine to it...
On 2/18/20 1:45 PM, Anders F Björklund wrote:
Ezequiel Aguilar wrote:
Is this a valid approach for running Podman in MacOS ? https://developers.redhat.com/blog/2020/02/12/podman-for-macos-sort-of/ It should be, the intention is to provide a "Podman Toolbox"...
Not everyone likes VirtualBox, but QEMU support is also included.
It is possible to make it accelerated on the Mac, similar to KVM: https://github.com/boot2podman/machine/issues/5#issuecomment-548442359
Both VirtualBox and QEMU should work on all the three platforms.
There is still some work to do, with the other 3 "machine" drivers.
And work is under way, to upgrade Tiny Core and to upgrade Fedora:
* Tiny Core Linux 11.0
* Fedora 31 Would love to have this replaced by Fedora CoreOS. But that might be quite a bit larger. Fits in to the Container story better though.
It seems similar to Docker Machine, and it works well for me.
Any thoughts? Glad you like it!
It's not really a native "Podman for Mac", but should be a start...
Like the article says, you can also run the full CRC on the Mac: https://developers.redhat.com/blog/2019/09/05/red-hat-openshift-4-on-your-la...
That will give you a more integrated product (i.e. no VirtualBox) It also requires a _lot_ more resources from your laptop, though.
Recently we are also added Podman support to Minikube, for v1.8.0.
This means that we have "podman-machine" and "minikube podman-env", which should be comparable to "docker-machine" and "docker-env" ?
You will get some basic Kubernetes support, also with Boot2Podman.
/Anders
PS. You can follow developer blog at https://boot2podman.github.io/
There will be some kind of hackathon, before foss-north conference.
PPS. There were more stuff in Docker for Mac and in Docker Desktop:
* https://www.docker.com/blog/docker-for-mac-windows-beta/
* https://www.docker.com/blog/get-to-know-docker-desktop/
I was just doing a Boot2Podman ISO, and then ported machine to it... _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Daniel Walsh wrote:
And work is under way, to upgrade Tiny Core and to upgrade Fedora:
* Tiny Core Linux 11.0
* Fedora 31 Would love to have this replaced by Fedora CoreOS. But that might be quite a bit larger. Fits in to the Container story better though.
If I understand things correctly, CRC (and OKD) uses Fedora CoreOS. So that might be an alternative here, for something based on CoreOS ? https://github.com/openshift/okd/blob/master/README.md#getting-started It would install a whole cluster instead of a container host, though. I wanted a LiveCD for a Boot2Podman alternative, not a cloud installer. So then it was easier with the Minishift (Origin) image as a base... https://github.com/minishift/minishift-fedora-iso The default is to use the CentOS 7 image, but it was too old for this. And the kickstart files are similar enough anyway, between the two ? https://github.com/minishift/minishift-centos-iso I think it should be _theoretically_ possible to use Fedora CoreOS. But you would have to create that initial Ignition FCC file somewhow: qemu-img create qcow2 -b fedora-coreos-qemu.qcow2 my-fcos-vm.qcow2 qemu-kvm -m 2048 -cpu host -nographic \ -drive if=virtio,file=my-fcos-vm.qcow2 \ -fw_cfg name=opt/com.coreos/config,file=path/to/example.ign The disk usage would also increase a lot (again), from 366M to 1644M. Compared to the original 117M (for TCL), that is almost 15 times... If you want an immutable container host OS for your public cloud, I'm sure it's a fine choice. But it's "overkill" just to run podman ? The same goes for k8s, in the shape of kubeadm. So I'm using k3s. It has a *quarter* of the memory footprint, while still using crio. And there's still some way to go, to get down to the sizes of dockerd (for machine) and containerd (for k3s). Currently, half: 58M boot2docker.iso 50M k3s So for now, I will "only" do the incremental OS version upgrades Sounds like a good opportunity for the Fedora community, though ? ;-) /Anders
On Tue, Feb 18, 2020 at 5:32 PM Anders F Björklund < anders.f.bjorklund@gmail.com> wrote:
Daniel Walsh wrote:
And work is under way, to upgrade Tiny Core and to upgrade Fedora:
* Tiny Core Linux 11.0
* Fedora 31 Would love to have this replaced by Fedora CoreOS. But that might be quite a bit larger. Fits in to the Container story better though.
If I understand things correctly, CRC (and OKD) uses Fedora CoreOS.
So that might be an alternative here, for something based on CoreOS ?
https://github.com/openshift/okd/blob/master/README.md#getting-started
It would install a whole cluster instead of a container host, though.
The CRC team is working on a "crc --podman start" command which will essentially "not enable" or "disable" the OpenShift cluster (depending on how you wnat to look at it. This has the advantages of: 1. Single engineering team for ISOs related to running containers (for customers) 2. Single thing for customers to download (two options on how to run it) 3. Easy path from Podman to OpenShift That is sort of the tentative plan for the product roadmap, but I totally understand wanting "just a bootable ISO" and I think what you state below should be fairly do-able.
I wanted a LiveCD for a Boot2Podman alternative, not a cloud installer. So then it was easier with the Minishift (Origin) image as a base...
https://github.com/minishift/minishift-fedora-iso
The default is to use the CentOS 7 image, but it was too old for this. And the kickstart files are similar enough anyway, between the two ?
https://github.com/minishift/minishift-centos-iso
I think it should be _theoretically_ possible to use Fedora CoreOS. But you would have to create that initial Ignition FCC file somewhow:
qemu-img create qcow2 -b fedora-coreos-qemu.qcow2 my-fcos-vm.qcow2 qemu-kvm -m 2048 -cpu host -nographic \ -drive if=virtio,file=my-fcos-vm.qcow2 \ -fw_cfg name=opt/com.coreos/config,file=path/to/example.ign
The disk usage would also increase a lot (again), from 366M to 1644M. Compared to the original 117M (for TCL), that is almost 15 times...
If you want an immutable container host OS for your public cloud, I'm sure it's a fine choice. But it's "overkill" just to run podman ?
The same goes for k8s, in the shape of kubeadm. So I'm using k3s. It has a *quarter* of the memory footprint, while still using crio.
And there's still some way to go, to get down to the sizes of dockerd (for machine) and containerd (for k3s). Currently, half:
58M boot2docker.iso 50M k3s
So for now, I will "only" do the incremental OS version upgrades Sounds like a good opportunity for the Fedora community, though ? ;-)
We love contributions :-)
/Anders _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- -- Scott McCarty, RHCA Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com Deeply understand the different between Portability, Compatibility, and Supportability with containers: http://bit.ly/2Qw3dJI
On 2/18/20 5:31 PM, Anders F Björklund wrote:
Daniel Walsh wrote:
And work is under way, to upgrade Tiny Core and to upgrade Fedora:
* Tiny Core Linux 11.0
* Fedora 31 Would love to have this replaced by Fedora CoreOS. But that might be quite a bit larger. Fits in to the Container story better though. If I understand things correctly, CRC (and OKD) uses Fedora CoreOS.
So that might be an alternative here, for something based on CoreOS ?
https://github.com/openshift/okd/blob/master/README.md#getting-started
It would install a whole cluster instead of a container host, though.
Yes this is getting smaller, and will probably be the Red Hat supported way of running podman/openshift on a MAC or Windows box.
I wanted a LiveCD for a Boot2Podman alternative, not a cloud installer. So then it was easier with the Minishift (Origin) image as a base...
SGTM
The default is to use the CentOS 7 image, but it was too old for this. And the kickstart files are similar enough anyway, between the two ?
https://github.com/minishift/minishift-centos-iso
I think it should be _theoretically_ possible to use Fedora CoreOS. But you would have to create that initial Ignition FCC file somewhow:
qemu-img create qcow2 -b fedora-coreos-qemu.qcow2 my-fcos-vm.qcow2 qemu-kvm -m 2048 -cpu host -nographic \ -drive if=virtio,file=my-fcos-vm.qcow2 \ -fw_cfg name=opt/com.coreos/config,file=path/to/example.ign
The disk usage would also increase a lot (again), from 366M to 1644M. Compared to the original 117M (for TCL), that is almost 15 times...
Yes, I want to encourage the Fedora CoreOS guys to shrink their image size (Drop Moby for example), Not sure what else is causing it to swell.
If you want an immutable container host OS for your public cloud, I'm sure it's a fine choice. But it's "overkill" just to run podman ?
Maybe, But if Fedora CoreOS is the going to be a preferred way of running containers, then we should make it more useful.
The same goes for k8s, in the shape of kubeadm. So I'm using k3s. It has a *quarter* of the memory footprint, while still using crio.
I am not arguing against you, I am just pointing out that we should have alternitives. Some people argue that k3s is not the same as k8s, in functionality.
And there's still some way to go, to get down to the sizes of dockerd (for machine) and containerd (for k3s). Currently, half:
58M boot2docker.iso 50M k3s
So for now, I will "only" do the incremental OS version upgrades Sounds like a good opportunity for the Fedora community, though ? ;-)
Yup
/Anders _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
participants (4)
-
Anders F Björklund -
Daniel Walsh -
Ezequiel Aguilar -
Scott McCarty