121–130 of 190 posts
Earlier quoted context omitted.
According to Apple software license agreements, yes, it is too much to ask. You can not legally run Mac OS on non-Apple hardware. But don't be sad, their new Mac Pro is fantastic .
The EULA says you can't run Mac OS on non Apple hardware? Pretty sure these terms are not enforceable in Europe so safe to ignore.
Earlier quoted context omitted.
The EULA says you can't run Mac OS on non Apple hardware? Pretty sure these terms are not enforceable in Europe so safe to ignore.
But how do you obtain the software in the first place?
Earlier quoted context omitted.
According to Apple software license agreements, yes, it is too much to ask. You can not legally run Mac OS on non-Apple hardware. But don't be sad, their new Mac Pro is fantastic .
It's an unenforced provision of the license agreement. No attorneys are recommending it but it's happening. I wouldn't start your own CI firm with it though. Unlike Microsoft, Apple has no motives to send the BSA after anyone. Pretty sure they've only used them for egregious copyright violations like the commercial Hackintoshes.
Earlier quoted context omitted.
Aren't you being a little too harsh? The Dockerfile automates the installation of libvirt and custom components to launch the VM so while the title might be misleading it is hardly "not adding" anything.
Docker is not adding anything whatsoever. The "dockerfile" could be converted with a simple macro into a plain bash script and it would literally be the same thing. The container is not abstracting anything here; you are using KVM of the host system. You even have to install more packages in the host than in the container. You could even just run the original script the Dockerfile is wrapping directly which will even…
Earlier quoted context omitted.
Docker keeps a history of changes to the container with layers, and you might arguably treat it like version control. maybe "docker history" ~ "git log"?? tags=branches? Docker isn't one thing, so it's ALL grey. It's not really make. It's not really a vm. It's not really even reproducible. One thing is for certain - it's hard to describe docker to new folks so they get it. "it's sort of like netflix, for cows, but in…
That's the most insane use of Docker I've ever heard of.
Can macOS virtual machines ever be performant enough to use as a workstation? So far I have only tried setting it up in VMWare and VirtualBox, the performance wasn't there but I haven't dedicated a GPU or drive to it yet. It would be so convenient to decouple macOS from Mac hardware.
The problem is cocoa performs terribly without gpu acceleration and nobody has figured out how to get around that, there are some tweaks to get OSX running in vmware and wherever else but you never wind up with working GPU acceleration so not only can you not change the resolution once you turn it on (iirc, may be wrong here), it's refresh rate is horrendous. If you ever used Windows before it installs the gpu driver…
Earlier quoted context omitted.
I don't care though. What I care about is that it's a pain in the butt to do CI/CD pipelines for an application with iOS/OSX support. So if someone has a headless OS X contraption on offer, I want to hear some more about it. The last time I set this up, a manager decided he wanted a laptop like the rest of us instead of the iMac he got. He asked semi-jokingly if someone wanted the machine for anything and I said "Yes…
That is exactly what I was thinking of. I don't want to buy dedicated hosts from MacStadium. I got native iOS builds and Unity buidls that would work well with this. Isolation is not as big of a concern. I too would like to hear if anyone has been able to pull this off. EDIT: And what about licensing?
However, if you buy a Mac, install Linux and use it to run the pipelines, that'd be strictly legal I believe.
Earlier quoted context omitted.
Docker is not adding anything whatsoever. The "dockerfile" could be converted with a simple macro into a plain bash script and it would literally be the same thing. The container is not abstracting anything here; you are using KVM of the host system. You even have to install more packages in the host than in the container. You could even just run the original script the Dockerfile is wrapping directly which will even…
Yes, Docker is effectively acting as the supervisor process for this container, only managing its process lifecycle and allowing easy removal/persistence.
My (linux) desktop has a macOS icon on it. I click on it. That starts a QEMU/KVM process which runs macOS. When I quit out of that, it is gone. When I click on it again, it runs again.
I suppose there are a few files floating around that persist between runs, and are not utterly trivial to manage. Just ... trivial to manage.