At the moment podman machine on macOS uses Qemu and their filesharing stack. Qemu allowed us to move quickly utilizing the same deployment stategy. However I work on CRC (a related project) and we have a driver based on virtualization framework using virtiofs. We hope to integrate this in `podman machine` soon as it will improve performance. Ideally we want to boot with the kernel and ramdisk provided by the image, though this isn't the case until macOS 13 (which brings EFI support). So, yes... hopefully soon. We just want to make sure we provide a stable and maintainable solution.
The virtiofs implementation we use is the native one provided by Apple according to our virtiofs spec. https://virtio-fs.gitlab.io/
You can try running https://github.com/crc-org/crc with the podman preset (!) to test it. It would not be exactly the same how podman machine will use it eventually, but might help to give an idea of performance or issues we can improve on. We have seen a lot of users being more than content as it also works in a vpn environment. Note that the CRC tool primarily aims at OpenShift deployment... This is a different preset (resource intensive). Only available as an installer with our tray (sorry about this).
The driver we use is https://github.com/crc-org/vfkit and I am sure Christophe could share a method to just run the VM with our driver. HMU by email if you prefer.
Thanks for the info. I don't actually use MacOS myself, but I'm interested in getting faster userspace networking and filesystem sharing for Linux and Windows hosts. virtiofs is interesting but it's unfortunate that it requires a daemon and AFAIK doesn't run on Windows hosts.
Right. HyperV only does eh... Well, they do 9P for WSL2, but not for HyperV itself. This is one of our issues. We work with the virtiofs team to get this resolved, but their implementation targets Linux first. We hope to see Microsoft adopting this too. We are glad to help. Especially as the current 9P implementation for WSL2 has known syncing and performance issues. On a VM you would have to resort to CIFS, sshfs or something else... Which are all not ideal for locally attached storage
Impact of the bugs in OpenSSL are so significant, that they always end up in to the news.
BearSSL is still a quite little project compared to it, and because of that no CVE:s are being made if the author finds a bug by themself from his own code.
On the other hand, every bug in OpenSSL gets CVE mark and will end up into the news.
It gives distorted view and comparison of the software quality between many projects.
I think that's because maintainers consider tickets as action items for them personally instead of treating them as feedback documenting known issues(sometimes with workarounds) for their users. I think DeVault put it very well a while back: a ticket is the place where the community can gather and exchange feedback on a perceived issue with a project (I'm paraphrasing).
With the exception of illegal content this is how it should be. “I don’t like this so I’m going to block it so I don’t have to look at it again” rather than “I don’t like this so nobody should be allowed to look at it”.
I'm aware. I simply prefer Newpipe because it has roughly the same functionality, is more lightweight and is open-source (+ it's on F-Droid so I can easily update it along with all my other apps).
Have your runWarm sleep for 500ms and execute 50 of them concurrently. As long as none of the functions are finished and you start a new one you get a new instance, at least that's what I think.
You can get 50 hot instances that way no?
I'd rather scale per connections. Have a lambda instance do 50 concurrent requests. Something like https://fly.io but cheaper.
Does anyone know how well Podman performs on Mac? Especially file sharing.
Edit: A quick Google led me back to this HackerNews comment[1]. Looks like Docker for Mac is faster.
[0] https://www.docker.com/blog/speed-boost-achievement-unlocked...
[1] https://news.ycombinator.com/item?id=32307595