Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS in QEMU in Docker

github.com

Post reply on HN
Print view View original

181–190 of 199 posts

Re: macOS in QEMU in Docker

#181

Post by oldandboring »

I set this up a few months ago as an experiment. Worked pretty well until I discovered that for iMessage to work, the application phones home to Apple using your hardware IDs, and this project uses fake values. At that point I started spiraling down the Great Waterslide of Nope, slowly discovering that the fake values are flagged by Apple and they will, as a consequence, flag your iCloud ID as a potential spammer, limiting your access from other devices. Your only option is to use a hardware ID generator script they vaguely link out to, and you can just keep trying values until you find one that "works", but there's not actually a good signal that you found one that works and isn't harming your iCloud reputation.

Worked really great otherwise, though. Very useful in a pinch.

Re: macOS in QEMU in Docker

#182

Post by judge2020 »

oldandboring wrote: post #181

I set this up a few months ago as an experiment. Worked pretty well until I discovered that for iMessage to work, the application phones home to Apple using your hardware IDs, and this project uses fake values. At that point I started spiraling down the Great Waterslide of Nope, slowly discovering that the fake values are flagged by Apple and they will, as a consequence, flag your iCloud ID as a potential spammer, li…

The "keep cycling HWIDs until one works" thing was also common to get Hackintosh iMessage to work, you'd be able to check if it works by going to checkcoverage.apple.com. I quickly realized it's easier to copy the Serial from a old but real Mac.

But I think this tool is more useful for things like build scripts (that rely on proprietary macOS frameworks) more than it is for actually using it like a personal computer.

Re: macOS in QEMU in Docker

#183

Post by judge2020 »

acka wrote: post #157

Somewhat off topic but still highly relevant for people who actually want to use projects like this: why oh why do so many build recipes such as Dockerfiles insist on pulling random stuff off the internet as part of the build process? For example, the Dockerfile in this project pulls in two Git repositories and a script at build time. Besides the obvious build failures on heavily sandboxed build servers with no acces…

Probably mostly to retain organization (via separate git repos) - in lieu of cloning stuff in Dockerfile, you end up needing a pre-build instruction of "when you clone use --recursive or do git submodule init to get the other repos into your CWD".

Re: macOS in QEMU in Docker

#184

Post by judge2020 »

yao420 wrote: post #81
prmoustache wrote: post #12

Is the redistribution of MacOS images allowed by the license or is this project distributing illegal copies in plain sight on docker hub?

Idk but Correlium virtualizes iOS instances and was sued by Apple before settling the case.

Correlium was a big commercial player and made headlines. Anyone using this privately (and especially non-commercially) probably isn't at risk of action from Apple, although I wouldn't be surprised if Apple eventually tries to go after publicly hosted images.

Re: macOS in QEMU in Docker

#185

Post by mynameisvlad »

resource_waste wrote: post #178
mynameisvlad wrote: post #130

Earlier quoted context omitted.

"Sorry a decade of use is not enough to be considered an expert. Also your experience is useless because it's on a distro I don't like." This is just pointless gatekeeping doubled down on at this point. People can be experts and use Kubuntu. People can be veterans and use Ubuntu. People can be absolute beginners and use Arch or OpenSUSE or literally any other distro. Use of distro is in no way shape or form indicativ…

Debian-family distros are literally outdated. Its not even gatekeeping in 2024. Linux pros are avoiding debian-family. Why would you use a buggy, slow, outdated distro when we have fast, modern, and fewer bugs? This is an ignorance thing, much of the linux community repeats what they did in the past, afraid to change.

> It’s not even gatekeeping in 2024. Linux pros are avoiding debian-family.

You’re not a “Linux pro” (not that that’s a thing in the first place ffs), so your opinion doesn’t matter, as much as you might think it does.

Glad to see pointless rabid fanaticism is still a thing in 2024, even in the Linux community.

Honestly, if you care this much about what distro someone uses, you need to get a life. This is by far the most pointless hill to die on.

Re: macOS in QEMU in Docker

#186

Post by imglorp »

acka wrote: post #157

Somewhat off topic but still highly relevant for people who actually want to use projects like this: why oh why do so many build recipes such as Dockerfiles insist on pulling random stuff off the internet as part of the build process? For example, the Dockerfile in this project pulls in two Git repositories and a script at build time. Besides the obvious build failures on heavily sandboxed build servers with no acces…

How is this different from JS pulling in tens of thousands of dependencies to display a web page?

In the 80s we envisioned modular, reusable software components you drop in like Lego bricks (we called it CASE then), and here we have it, success! Spoiler, it comes with tradeoffs...

Re: macOS in QEMU in Docker

#187

Post by [deleted] »

nine_k wrote: post #13

So, to clarify things: it's QEMU running in a container, and macOS running under QEMU inside it. This is really nice WRT the ease of installation: no manual setup steps and all. This likely expressly violates the [macOS EULA], which says: «you are granted a limited, non-exclusive license to install, use and run one (1) copy of the Apple Software on a single Apple-branded computer at any one time» — because the point…

[deleted]

Re: macOS in QEMU in Docker

#189

Post by ramses0 »

Modified3019 wrote: post #127
ramses0 wrote: post #60

Earlier quoted context omitted.

The Tao of Programming, 7.3: """ "Corporate Headquarters has commanded," continued the magician, "that everyone use this workstation as a platform for new programs. Do you agree to this?" "Certainly," replied the master, "I will have it transported to the data center immediately!" And the magician returned to his tower, well pleased. Several days later, a novice wandered into the office of the master programmer and s…

I don’t understand what this is trying to say.

Back in 'ye olden days, people used to print out programs... nay, they even used to _hand-write!_ programs before they began typing, because keyboard-time was valuable (nevermind compilation/computation/debugging time).

Serial ports were slow, grep wasn't really a thing, so having a printout (or "listing") of your program was a more efficient way (or only way!)to debug your program after the fact. https://www.youtube.com/watch?v=tJGrie7k97c

Back in the 90's, I had some programming classes in high school where there were 30 chairs, but 15 computers (around the edge)... bring your own 360kb floppy disk! So you had a real incentive (and a strict teacher) who insisted that you wrote out your program ahead of time, show it to her for a first-pass/feedback, and _then_ you'd get to go type it on the computer and see if it worked. Submissions were via printouts (of the program, aka "listing", along with the output) which she then took home and graded.

The whole document IMHO is worth a read, but is definitely a product of it's time (70's/80's/90's). https://en.wikipedia.org/wiki/The_Tao_of_Programming

Stick tongue firmly in cheek, empty your cup, and enjoy the ride!

Edit: ...and the relationship to the cantankerous original comment who "couldn't figure why they'd want to run OSX?", this is the zen-koan sarcastic response of: "use it as a platform for development" (ie: stack your papers on top if it)

Re: macOS in QEMU in Docker

#190

Post by [deleted] »

oldandboring wrote: post #181

I set this up a few months ago as an experiment. Worked pretty well until I discovered that for iMessage to work, the application phones home to Apple using your hardware IDs, and this project uses fake values. At that point I started spiraling down the Great Waterslide of Nope, slowly discovering that the fake values are flagged by Apple and they will, as a consequence, flag your iCloud ID as a potential spammer, li…

[deleted]
Post reply on HN