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

macOS Containers v0.0.1

macoscontainers.org

Post reply on HN
Print view View original

71–80 of 374 posts

Re: macOS Containers v0.0.1

#71

Post by urxvtcd »

devsda wrote: post #45
rafaelmn wrote: post #30

Earlier quoted context omitted.

>Wouldn't a Linux device, or Linux running on a Mac suit you better? Maybe they want a unixy desktop with working sound ? Half joking, but that's my use case - homebrew is pretty great, most developers use a Mac in my domains of interest so it's always supported. Linux is just too much work (and I'm using Fedora on my desktop). SIP is just false positives and annoyance. I'm on the fence about M/ARM switch since I sti…

> Maybe they want a unixy desktop with working sound ? In my experience, this has not been an issue for the past 10-15 years atleast. Before that there were some problems with few (external) soundcards or random cpu spikes with the mixers. However, the UX can still improve. Switching audio outputs with multiple outputs like external displays etc is not very smooth or intuitive. Some bluetooth headsets have issues but…

Anecdotal evidence, but here it goes.

I moved from Linux to M1 MacBook recently. I know my greps and vims, but I was tired of audio glitches during high CPU usage, system not waking up from sleep, total OS freezes, super loud fans, and so on.

Now I get none of that. I don't think I've ever heard the fans. Audio just works, everything is super snappy. It always wakes up. I'm no longer afraid of bluetooth.

And on top of that, setting my $DAYJOB VPN took three minutes and it just works, where on Linux I had constant problems with DNS breaking, and setting it up was always an hour of work, praying I got the config files right this time.

It really seems to be "unixy desktop with working sound", the best of both worlds.

Re: macOS Containers v0.0.1

#72

Post by rafaelmn »

devsda wrote: post #45
rafaelmn wrote: post #30

Earlier quoted context omitted.

>Wouldn't a Linux device, or Linux running on a Mac suit you better? Maybe they want a unixy desktop with working sound ? Half joking, but that's my use case - homebrew is pretty great, most developers use a Mac in my domains of interest so it's always supported. Linux is just too much work (and I'm using Fedora on my desktop). SIP is just false positives and annoyance. I'm on the fence about M/ARM switch since I sti…

> Maybe they want a unixy desktop with working sound ? In my experience, this has not been an issue for the past 10-15 years atleast. Before that there were some problems with few (external) soundcards or random cpu spikes with the mixers. However, the UX can still improve. Switching audio outputs with multiple outputs like external displays etc is not very smooth or intuitive. Some bluetooth headsets have issues but…

The sound is an internal meme where the linux devops would regularly have to drop off calls to talk (restart to unmute :)).

On my desktop I couldn't even boot installer without running with safe mode, otherwise I'd just get stuck on a blank screen (ancient 1050 TI GPU and standard desktop components otherwise, so not exotic/new stuff).

I've used linux desktop for >decade and Gnome shell feels like home but these days I feel like I don't have the time for linux adventures. Maybe I'll mix it up with my next device, but I'm not reading great things about AMD power modes and Linux.

Re: macOS Containers v0.0.1

#73

Post by orf »

hamandcheese wrote: post #68
kowlo wrote: post #56

Earlier quoted context omitted.

Perhaps they are talking about Homebrew the package manager [1]. [1] https://brew.sh

I wonder what people mean when they say "Homebrew is pretty great", I do not wonder what they mean when they say "Homebrew".

They mean that they have an overall positive opinion of Homebrew, more than “not bad” but less than “amazing”.

Re: macOS Containers v0.0.1

#74

Post by tomduncalf »

hamandcheese wrote: post #47
rafaelmn wrote: post #30

Earlier quoted context omitted.

>Wouldn't a Linux device, or Linux running on a Mac suit you better? Maybe they want a unixy desktop with working sound ? Half joking, but that's my use case - homebrew is pretty great, most developers use a Mac in my domains of interest so it's always supported. Linux is just too much work (and I'm using Fedora on my desktop). SIP is just false positives and annoyance. I'm on the fence about M/ARM switch since I sti…

> homebrew is pretty great I hear this said a lot in passing, and I'm really curious what people mean when they say this.

I mean, it installs stuff more or less reliably for me so I’d say that’s pretty great. I’m sure it has issues (I’ve had problems trying to install old versions of packages for example) but I don’t think I’ve ever had “brew install ” fail to install what I wanted

Re: macOS Containers v0.0.1

#75

Post by hizanberg »

hamandcheese wrote: post #68
kowlo wrote: post #56

Earlier quoted context omitted.

Perhaps they are talking about Homebrew the package manager [1]. [1] https://brew.sh

I wonder what people mean when they say "Homebrew is pretty great", I do not wonder what they mean when they say "Homebrew".

It does what it says on the tin and installs the plethora of software available on homebrew with a simple command, which is pretty great

Re: macOS Containers v0.0.1

#76

Post by prmoustache »

caveat: this is based on rund. Extract from the readme:

rund is an experimental containerd shim for running macOS containers on macOS.

rund doesn’t offer the usual level of container isolation that is achievable on other OSes due to limited macOS kernel API.

What rund provides:

    Filesystem isolation via chroot(2)

    Cleanup of container processes using process group

    OCI Runtime Specification compatibility (to the extent it is possible on macOS)

    Host-network mode only

    bind mounts

Re: macOS Containers v0.0.1

#77

Post by tiagod »

steeleduncan wrote: post #69
jamil7 wrote: post #51

Earlier quoted context omitted.

In the context of an internal CI or something, it's probably fine.

Given that the vast majority of CI runs on linux without any equivalent of SIP, I'd have thought it were a complete non-issue

You might want to run CI/CD on your Mac builds

Re: macOS Containers v0.0.1

#78

Post by astrange »

bzzzt wrote: post #26
skibz wrote: post #3

System Integrity Protection sounds really important. What does it do normally, and why does this tool require it to be disabled?

It's meant to protect the base OS from persistent malware infections. https://support.apple.com/en-us/102149

Also against accidentally deleting /usr.

Re: macOS Containers v0.0.1

#79

Post by anonymoushn »

hamandcheese wrote: post #68
kowlo wrote: post #56

Earlier quoted context omitted.

Perhaps they are talking about Homebrew the package manager [1]. [1] https://brew.sh

I wonder what people mean when they say "Homebrew is pretty great", I do not wonder what they mean when they say "Homebrew".

For example people do not use homebrew to install python3 on a fresh install of mac os and get a python that spews a bunch of messages to stderr about the version of libc6.so and cannot speak TLS.

Re: macOS Containers v0.0.1

#80

Post by pard68 »

highwaylights wrote: post #21
perryizgr8 wrote: post #15

Earlier quoted context omitted.

> "Disable System Identity Protection." This is the first thing I do on any Mac OS system before I start using it.

This kind of makes me wonder why you'd have a Mac at all (I'm sure there are use cases). Wouldn't a Linux device, or Linux running on a Mac suit you better? For me, the security picture is one of the main features of the eco-system even if it's very restrictive - disabling SIP undermines it more or less completely.

Work gives me a laptop, I use it. I'd prefer Linux, but that's not what I get.
Post reply on HN