-
Notifications
You must be signed in to change notification settings - Fork 33
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
Is only FreeBSD on scope? #41
Comments
Apologies for the lengthy delay in getting back to you. runj is focused on FreeBSD for now as I only have a FreeBSD VM set up to test with (and I'd rather get runj more complete before starting work on another OS). However, if the patches to make runj work on DragonFly BSD are relatively small, that could be reasonable to incorporate into runj. What are some of the differences in approaches between FreeBSD and DragonFly BSD with respect to jails? |
Basically, DragonFly BSD jails are FreeBSD's late 4.x or early 5.x jails. We haven't ported new changes from FreeBSD and we haven't developed jails further yet. Now I'm thinking it might just be easier for everyone that we add some sort of compatibility layer with the idea of being able to run whatever that runs for FreeBSD. In any case this was just a thought that I wanted to get input on. Many thanks! |
I think it's gonna be really tricky without vnet support |
Can you expand on that a bit? Thanks! |
VNET(9) is the way we isolate networking between jails, but it looks like you can create containers without network isolation, if I'm reading this right Lines 82 to 108 in 8ab46e9
|
There are other FreeBSD-based OSes like DragonFly BSD that will likely take a, somewhat, different approach wrt jails and that don't have a linux compatibility layer.
I'm wondering if such would be considered, ofc by submitting PRs ourselves.
The text was updated successfully, but these errors were encountered: