Opencore-Legacy-Patcher
Docker-OSX
Our great sponsors
Opencore-Legacy-Patcher | Docker-OSX | |
---|---|---|
326 | 132 | |
57 | 35,279 | |
- | - | |
8.2 | 5.7 | |
about 3 years ago | 19 days ago | |
Python | Shell | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Opencore-Legacy-Patcher
- Where else to go for specific OpenCore support?
-
macOS Sonoma is setting records for update size
At a guess I would say probably using OCLP - https://github.com/dortania/OpenCore-Legacy-Patcher - lots of life left in old Mac’s using that tool !
- 1.2 coming soon?
-
I need help with touch ID
I had this issue, too. But luckily, I've got a solution. First, you'll need to check your MacOS Sonoma version. If you're using 14.1 beta, this method will NOT work. In such cases, I recommend installing the official 14.0. Thankfully, this commit (https://github.com/dortania/OpenCore-Legacy-Patcher/commit/1aee2e5dfa12d10e218a51e4151ac2e96705ae9e) solved the problem! However, the latest OCLP 1.0.1 still doesn't have it. To use it, you can build OCLP from code or use the OCLP Nightly link found here. After you find the nightly link and download OCLP, build it onto your MBP, and after rebooting, install the patches. If you look carefully, you'll see that 'experimental T1 Patches' will be available in the list of post-installation patches.
- MBP with T1 Touch ID Working on Sonoma!
-
Late 2010 MacBook Air (MacBookAir3,1): Guidance needed
From what I've assessed reading other posts, Monterey (Ventura has USB & stability issues) with OCLP 0.6.7 is the most stable install for this device (have not yet seen any reports using OCLP 1.0+, although happy to see some new non-Metal fixes going in). This is a bit of a bummer, as Monterey will not likely receive updates past end of 2024 (next year).
- Enable wifi in Sonoma with Fenvi T919
-
OpenCore Legacy Patcher project brings macOS Sonoma support to 16-year-old Macs
I'm not taking a position on OCLP being trustworthy or not, but at least the project appears to be 100% open source [0], which is more than we can say about Apple.
[0] https://github.com/dortania/OpenCore-Legacy-Patcher
-
macOS Sonoma is available today
Have you explored https://github.com/dortania/OpenCore-Legacy-Patcher?
I have used it before and, in my experience and everyone else I know who has used it, the vast majority of time the newer versions run absolutely fine with no issues. Occasionally some newer features don't work, but I'd but confident that 2015/2017 iMacs would be able to run the latest version no problem.
-
List of currently supported outdated Mac models by OLCP for macOS Sonoma
Link to pull request to track OLCP Sonoma support state, you can also read more info there: https://github.com/dortania/OpenCore-Legacy-Patcher/pull/1077
Docker-OSX
-
GitHub Actions as a time-sharing supercomputer
Running macOS legally requires real mac servers and a bespoke storage solution: https://www.datacenterdynamics.com/en/analysis/not-just-stac...
A self-hosted macOS runner will be more economical in the long-run, if you have a spot you can hook it up at, or if you're fine doing things less than legally, you can use https://github.com/sickcodes/Docker-OSX.
- Docker-OSX · Follow @sickcodes on Twitter
- É caro programar do jeito “honesto”
-
Caso você não queira comprar um Mac mas ainda queira o sistema, agora dá pra rodar MacOS dentro do Docker
Repositório Docker-OSX - Guidelines, troubleshooting, comandos
- Can i run a Hackintosh VM on my homelab and stream it to my pc ?
-
macOS Containers v0.0.1
> What's the licensing situation on this?
1. This project didn't take explicit permission from Apple to redistribute binaries
2. There are multiple jurisdictions where you don't need to explicitly have such permission, it is implied by law
3. Usage of this software implies you already have macOS system. I'm not a lawyer, but it looks to be covered by section 3 of macOS EULA.
4. There are existing precedents of redistribution of macOS binaries for multiple years aready:
- https://github.com/cirruslabs/macos-image-templates/pkgs/con...
- https://hub.docker.com/r/sickcodes/docker-osx
- https://app.vagrantup.com/jhcook/boxes/macos-sierra
And so on.
-
Android Dev account terminated after 12 years for violating “Stalkerware policy”
Google is “friendlier”, because they run some automated scans on the apk and you’re good. Apple has humans run your app to confirm it does what you claim, as well as a battery of automated scans and since they are using the app I’d imagine they look at network traffic as much as possible. I know iOS isn’t shielded from malicious apps, but there’s malware and viruses all over the play store. That’s because it’s free and “friendlier”.
> At Apple things have gotten way worse. Trying to automate release building is practically impossible and will require hours or CI pipeline debugging with error messages that don't mean what they say.
This isn’t Apple’s fault… every build system sucks up a decent amount of time during initial setup. You can cut down massive amounts of time between iterations by adding some common optimizations:
1. Cache artifacts when that step or job succeeds, so if a subsequent step/job fails, you can adjust it and start up where you left off, using the caches artifact to restore the workspace state. This complicates debugging efforts and I personally don’t do any optimization until the pipeline is reliably green each time. I just deal with slow builds and switch to other stuff or work ahead while they run.
2. Fail fast. The CI run should bail out if any critical steps don’t pass, so anything further down doesn’t run for no reason, burning compute time and delaying queued jobs waiting for a runner. While developing the pipeline, watch the logs and when you see something you don’t like, slap the cancel button, or collect a couple things you need to change and iterate with passes with 2-3 changes.
3. Use adequately spec’s hardware. Xcode is resource heavy and compiles need plenty of memory and cpu cores. Play around with what is a good compromise between power and cost. See if your project builds faster with more cpu cores, or faster cpu cores, etc.
> At least Googles process is quite simple and can be dockerized.
One man’s simple is another man’s “practically impossible”. Simple comes from familiarity and confidence. Anyway, you can totally run your builds in docker if you want to, and many do, but I’d personally not introduce more complexity until you have your pipelines running the slow way with the least amount of mental modeling to do. Once you know it all works, then have a go at running the build you know is good, inside a docker container (which in this case is just packing up kvm/qemu/libvirt to facilitate the running of a vm back on the host, but it means you can run mac containers on Linux runners, which will be much cheaper than Mac runners since those are usually Mac hardware)
https://github.com/sickcodes/Docker-OSX
> Also why do I have to pay Apple $125 a year when it costs $100 in the US? The exchange rate from CHF to USD should be in my favor.
Couple theories. 1. They have additional processing or tax expenses when dealing with your currency which they aren’t going to eat the cost of. 2. The higher price could be to deter abuse if for some reason there is an abnormal amount originating from accounts who pay with that currency.
-
Lima: A nice way to run Linux VMs on Mac
You can use qemu/libvirt/kvm on any Linux host to run macOS pretty easily these days[1]. I run Ventura on unraid with nvidea gpu passthrough and it’s been fairly painless.
You can also run macOS in docker, but it’s ultimately running through qemu/kvm as well[2]
1. https://github.com/kholia/OSX-KVM
2. https://github.com/sickcodes/Docker-OSX
-
Should I buy an iPhone or wait for beeper / sunbird
It would be a better idea to setup bluebubbles if you really want imessages while you wait, if you have an old laptop that you can use as a macos server. https://github.com/sickcodes/Docker-OSX is a brilliant solution for macos vm as a docker container. mac hardware not required
- Is it worth buying an iPhone to test on safari?
What are some alternatives?
Geforce-Kepler-patcher - Install Nvidia binaries files on Snapshot disk for macOS Monterey 12
lima - Linux virtual machines, with a focus on running containers
Patched-Sur - A simple but powerful patcher for macOS Big Sur.
macOS-Simple-KVM - Tools to set up a quick macOS VM in QEMU, accelerated by KVM.
big-sur-micropatcher - A primitive USB patcher for installing macOS Big Sur on unsupported Macs
redroid-doc - redroid (Remote-Android) is a multi-arch, GPU enabled, Android in Cloud solution. Track issues / docs here
OpenCore-Install-Guide - Repo for the OpenCore Install Guide
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
bigmac - Big Mac, macOS 11 Big Sur and macOS Monterey disk installer and back up tool for Intel based Macs
macos-virtualbox - Push-button installer of macOS Catalina, Mojave, and High Sierra guests in Virtualbox on x86 CPUs for Windows, Linux, and macOS
ryzen-hackintosh - OpenCore EFI for AMD Ryzen Hackintosh
podman-macos - 📦 Podman frontend for macOS