Linux Container Internals

Re:Linux Container Internals by Demiurge on Wednesday December 21, 2016 @03:40PM (#13232453)

The url is correct, 'Docker-internals', but the title, and further equivocation of 'Linux Containers' and 'Docker', is a bit confusing. I'm a happy lxc/lxd user, and had to stop reading because of the cognitive dissonance.

[ Parent | on HN ]

Re:Linux Container Internals by so0k on Wednesday December 21, 2016 @05:18PM (#13233152)

Good point, updated the title. Thanks for the comments (and yes it's almost a year ago I wrote this post)

[ Parent | on HN ]

Re:Linux Container Internals by Demiurge on Wednesday December 21, 2016 @08:06PM (#13233999)

Thanks, feels like the nitpick, but I gave it another go, and I see some other changes now? Seems like a great amount of information.

[ Parent | on HN ]

Re:Linux Container Internals by so0k on Wednesday December 21, 2016 @08:29PM (#13234081)

don't think there are other changes - https://github.com/docker-saigon/docker-saigon.github.io/com...

[ Parent | on HN ]

Re:Linux Container Internals by Demiurge on Wednesday December 21, 2016 @08:45PM (#13234144)

neatz, I guess I just need to be more patient and set my expectations :)

[ Parent | on HN ]

Re:Linux Container Internals by agumonkey on Wednesday December 21, 2016 @04:26PM (#13232762)

I also thought it was about LXC. Sad.

[ Parent | on HN ]

Re:Linux Container Internals by skeptic2718 on Wednesday December 21, 2016 @07:36PM (#13233878)

Why is it sad?

[ Parent | on HN ]

Re:Linux Container Internals by dozzie on Thursday December 22, 2016 @06:21AM (#13236537)

Because LXC on a technical level is much simpler, doesn't make mess in network and filesystem setup, and is easy to understand. Docker does some heavy magic for things to work for programmers (the ones who can't be bothered to learn how ethernet bridging or IP routing work), so the whole thing feels brittle.

In short, LXC is vastly underappreciated.

[ Parent | on HN ]