Containers and kubernetes are red flags and I treat them as "no hires" if talked in interviews as if they are the end all be all. It tells me that the person in question has 0 to negative ops knowledge.
Linux containers in 500 lines of code (2016)
21–30 of 31 posts
Re: Linux containers in 500 lines of code (2016)
#22I'm wondering if MacOS has the requisite system calls to have its own native containers, I imagine it does, Darwin being based on BSD. Are there any products that use that functionality?
Re: Linux containers in 500 lines of code (2016)
#23Simple unprivileged container runtimes:
https://github.com/NVIDIA/enroot
https://github.com/hpc/charliecloud
Re: Linux containers in 500 lines of code (2016)
#24I'm wondering if MacOS has the requisite system calls to have its own native containers, I imagine it does, Darwin being based on BSD. Are there any products that use that functionality?
Not sure how you get from Darwin being based on BSD to Darwin should be able to support something which heavily relies on Linux specific functionality to the point where even Freebsd having trouble https://wiki.freebsd.org/Docker
Sure with enough changes MacOS could support it, but then with enough changes to anything, so that is not really a sensible measure.
Re: Linux containers in 500 lines of code (2016)
#25I'm wondering if MacOS has the requisite system calls to have its own native containers, I imagine it does, Darwin being based on BSD. Are there any products that use that functionality?
Not sure how you get from Darwin being based on BSD to Darwin should be able to support something which heavily relies on Linux specific functionality to the point where even Freebsd having trouble https://wiki.freebsd.org/Docker Sure with enough changes MacOS could support it, but then with enough changes to anything, so that is not really a sensible measure.
The question wasn't about running docker on *BSD or macOS, but rather running some form of native container. Native containers don't rely on linux, they rely on the kernel having some form of containerization primitive.
FreeBSD has jails, which are a native type of container on freebsd.
However, BSD operating systems are really different from each other. OpenBSD doesn't have jails or anything too like containers, and macOS does have sandboxes (which are kinda like a container in some way), but no proper containers.
Docker isn't really related to the question of whether a native container solution exists on non-linux platforms.
Re: Linux containers in 500 lines of code (2016)
#26I'm wondering if MacOS has the requisite system calls to have its own native containers, I imagine it does, Darwin being based on BSD. Are there any products that use that functionality?
Re: Linux containers in 500 lines of code (2016)
#27I'm wondering if MacOS has the requisite system calls to have its own native containers, I imagine it does, Darwin being based on BSD. Are there any products that use that functionality?
Kind of but with limitations. You have chroot, which may or may not be secure, app sandbox which is quite powerful (but best used without chroot). No process namespaces or jails, very limited network isolation. No bind mounts. Overall very limited, you could do something but it woild be quite different.
Re: Linux containers in 500 lines of code (2016)
#28I'm wondering if MacOS has the requisite system calls to have its own native containers, I imagine it does, Darwin being based on BSD. Are there any products that use that functionality?
Not sure how you get from Darwin being based on BSD to Darwin should be able to support something which heavily relies on Linux specific functionality to the point where even Freebsd having trouble https://wiki.freebsd.org/Docker Sure with enough changes MacOS could support it, but then with enough changes to anything, so that is not really a sensible measure.
Darwin is the generic name for the open source posix OS that’s the basis for MacOS (and others).
It would be more appropriate to compare the XNU micro kernel used in Darwin to the Linux kernel used in GNU/Linux in your analogy.
Re: Linux containers in 500 lines of code (2016)
#29> pivot_root is a system call lets us swap the mount at / with another. Glibc doesn't provide a wrapper for it, but includes a prototype in the man page. I don't really understand, but OK, we'll include our own.
Probably because pivot_root is a speciality that is used in initramfs boostrapping and is exposed to that scriptology via the pivot_root program that comes from the util-linux project.
Re: Linux containers in 500 lines of code (2016)
#30Earlier quoted context omitted.
Only the first few lines of the script look dense. Everything else looks normal to me.
Stuff like https://github.com/p8952/bocker/blob/master/bocker#L94 is super dense. I might write that something like: cid="$( ps o ppid,pid | grep "^$( ps o pid,cmd | grep -E "^\ *[0-9]+ unshare.*$1" | awk '{print $1}' )" | awk '{print $2}' )"
Dang, didn't expect the downvotes for sharing my bash coding style. :(