3 ms·
If you really want good adoption, you’ll have to figure out a way for devs to try it out without first having to disable SIP. Is this related to the code you t
by ayewo 3y ago
If you really want good adoption, you’ll have to figure out a way for devs to try it out without first having to disable SIP.
Is this related to the code you tried to have merged here: https://github.com/containerd/containerd/pull/8789 https://github.com/containerd/containerd/pull/8789 ?
- slonopotamus 3y agoNope, that PR was an attempt to upstream my changes: https://github.com/macOScontainers/containerd/commits/macos https://github.com/macOScontainers/containerd/commits/macos Vanilla containerd cannot mount anything on macos. > If you really want good adoption, you’ll have to figure out a way for devs to try it out without first having to disable SIP. I can't stress enough how I also would like it to work with SIP enabled!
- capableweb 3y agoSounds like if Apple wants developers who wants to use containers natively, they need to address the problem of not being able to offer this feature without disabling SIP. No matter what you or I think about what's needed for adoption, technical problems get in the way of the tool working with SIP, so seems it's in Apple's ball court really.
- reddit_clone 3y agoIn corporate managed laptops it may not be an option to disable SIP.
- xp84 3y agoUnderstatement of the year. I am sure there are some places where being caught doing something like that (without authorization) could result in one of those “my hands are tied, I have to fire you” situations. Think places where security is a big deal, like finance, military, aerospace, critical infrastructure etc.