2 ms·
> Would I be distributing parts of macOS in my containers? Unless you're producing fully static binaries (or static enough that they don't bind to non-redistri
by lloeki 3y ago
> Would I be distributing parts of macOS in my containers?
Unless you're producing fully static binaries (or static enough that they don't bind to non-redistributable things) it'd be a yes (it would not be much of a container if it needed non-packaged things)
The screenshot points out a ghcr.io URL that lands on these packages: https://github.com/orgs/macOScontainers/packages?repo_name=macos-jail https://github.com/orgs/macOScontainers/packages?repo_name=m...
Edit: There's a note here†, so at least there is some consideration for licensing. No idea if it holds ground.
† https://github.com/macOScontainers/macos-jail/blob/9b1d5b141091c795887b35dd0289d3fe363dd631/README.md#macos-jail https://github.com/macOScontainers/macos-jail/blob/9b1d5b141...
- donatj 3y agoCounting the hours until this gets DMCA'd out of existence
- lloeki 3y agoAnecdotally: - there has been images like that circulating on well-known platforms† for a long time. - I never heard of a single DMCA on any of these, even though they were on much clearer violation of the license. Apple might be pulling a Hackintosh manoeuvre here. † an example, there are many others: https://app.vagrantup.com/jhcook/boxes/macos-sierra https://app.vagrantup.com/jhcook/boxes/macos-sierra
- notnmeyer 3y agofolks have been building macos vm images, sharing them, and virtualizing macos on macos for a decade or so now. is this that much different?