Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS support #1270

Open
ianlewis opened this issue Nov 26, 2019 · 6 comments
Open

MacOS support #1270

ianlewis opened this issue Nov 26, 2019 · 6 comments
Labels
priority: p3 Low priority status: help wanted Extra attention is needed type: enhancement New feature or request

Comments

@ianlewis
Copy link
Contributor

gVisor running on MacOS could provide an environment for Mac users to develop and run Linux containers on a Mac machine without needing to install Linux via a VM or Docker for Mac etc.

Some investigation needs to happen in order scope out what would be needed.

@ianlewis ianlewis added type: enhancement New feature or request priority: p3 Low priority good first issue Good for newcomers status: help wanted Extra attention is needed and removed good first issue Good for newcomers labels Nov 26, 2019
@sbrki
Copy link

sbrki commented Apr 2, 2020

@ianlewis are you sure this would work? Linux syscalls could be translated into native Darwin syscalls by gvisor, but I think the host kernel (in this case Darwin) needs to have cgroups in order for this to work in the first place.

@ianlewis
Copy link
Contributor Author

ianlewis commented Apr 2, 2020

@psycadet Yeah, cgroups specifically may not be able to be supported natively. It may be that a virtualized shim (e.g. HyperKit) is needed like Docker for Mac or there may be other ways to make it work natively on a Mac. There will be a lot of challenges to be sure, but it would be an interesting feature if someone wanted to try and support it.

copybara-service bot pushed a commit that referenced this issue Nov 12, 2021
- Stub out sighandling functions with panics on Darwin
- Put Linux-specific errors into their own syserr file

Not sure how best to get automated tests running, so I'll leave that for a later
change.

Fixes #6839.
Related to #1270.

PiperOrigin-RevId: 409516969
copybara-service bot pushed a commit that referenced this issue Nov 22, 2021
Related to #1270.

PiperOrigin-RevId: 411648212
copybara-service bot pushed a commit that referenced this issue Nov 26, 2021
Part of #1270.

PiperOrigin-RevId: 410109169
@mauriciogg
Copy link

Hey @ianlewis did this ever get any traction?

@ianlewis
Copy link
Contributor Author

@mauriciogg @kevinGC has been looking at it and has done the work to get us closer to full Mac support so he's the one to ask.

@l1n
Copy link

l1n commented Oct 28, 2024

Interested in this again, if it's still being worked on!

@kevinGC
Copy link
Collaborator

kevinGC commented Oct 30, 2024

It's not currently, unfortunately. No reason it can't be done, it's just that nobody has had the time to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Low priority status: help wanted Extra attention is needed type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants