4 ms·
While this is interesting, it doesn't really show how containers actually work, only lists the specific syscall flags to tell Linux create one. A similar snipp
by devxpy 6y ago
While this is interesting, it doesn't really show how containers actually work, only lists the specific syscall flags to tell Linux create one.
A similar snippet[1] exists for go, and it doesn't do anything particularly special either.
I don't know, maybe David beazley has altered my sense of what "from scratch" means.
[1] https://gist.github.com/lizrice/a5ef4d175fd0cd3491c7e8d716826d27 https://gist.github.com/lizrice/a5ef4d175fd0cd3491c7e8d71682...
- sp332 6y agoThis is how containers work though. Or did you want more detail about the internals of pivot_root or something?
- devxpy 6y agoYes, something like that. Like here's David's "Build Your Own Async" [1], which I prefer over Philip's (still extremely good) "What the heck is the event loop anyway?" [2]. It's one thing to tell how something works, but to successfully show what the hell its actually doing under the covers, just conveys much more information. [1] https://www.youtube.com/watch?v=Y4Gt3Xjd7G8 https://www.youtube.com/watch?v=Y4Gt3Xjd7G8 [2] https://www.youtube.com/watch?v=8aGhZQkoFbQ https://www.youtube.com/watch?v=8aGhZQkoFbQ
- ape4 6y agoAgree, you can't make your own code to isolate from the OS. You need the OS to do that.