71–80 of 101 posts
First thanks, this was really interesting.
Sorry, I must not be that bright, I cannot guess your email from your username :-( (and I don't have a tumbler login, and you haven't enable dm from strangers on twitter), but I wanted to point at that you have a typo on slide 9, s/ journactl/journalctl/.
Earlier quoted context omitted.
How do you get boot2LXC working? Any docs, or does everyone have to DIY it all again? Is there an ecosystem around LXC that provides things like Flynn? I can do it all myself, but I can't do it, my development job, and be home for dinner at night. Like most tools today, the value is in the ecosystem, not the tool itself.
LXC is generic container technology like KVM OR Xen are generic virtualization technologies. LXC virtualizes the OS environment and gives you lightweight containers that you can seamlessly transition your VM workloads to, or use as a lightweight portable alternative to VMs, so its use case is general and not a narrow focus on paas or deployment centric technology. Users can then decide how they want to deploy. Docker…
I had noticed that too initially.
They had to minimize it because otherwise people would just say "why not just use LXC, what do I need the whale for?".
From the marketing standpoint it had to be "yeah that is complicated low level bearded guy stuff, you need cool easy slick stuff we provide".
Author here - I'm working on a blog post for this and didn't expect this to be posted on HN so soon, but I guess that's what I should expect for posting a link to it in another HN comment! :) These slides correspond to a workshop I conducted a week ago demonstrating the internals of Docker and how Docker containers can be run without using any of the Docker tools or runtime. Docker is a great tool, and I'm glad it's…
Off topic: how do I create slides like this? What did you use to create 'em?
Earlier quoted context omitted.
Or chroots, jails, libvirt-sandbox, etc etc.
chroot's aren't namespaced, which is a big important difference. Being able to kill the entire container by killing it's init process (and keep it's processes out of the host namespace) is a huge deal.
Sure they are. If you chroot apache to /var/www, then /var/www is now / in the chroot'ed namespace.
Earlier quoted context omitted.
What they mean is when the slides were made, Debian 8 was about to be released in "stable" with systemd. With debian 8 released the only oddball is ubuntu with their own early fork of systemd called upstart. It means from this day forward the things you see in the demo are already or inevitably available on every install of linux. You don't need to install anything special to do what he's doing there. http://upload.w…
"inevitably available on every install of linux" s/every/most. Slackware and a few others still do not use systemd and quite possibly never will.
I haven't used Docker myself. So what value add does Docker provide?
I should stress that last point - I dislike certain aspects of docker, but I love their system for building images. I want to somehow adapt it for building bare metal images.
Author here - I'm working on a blog post for this and didn't expect this to be posted on HN so soon, but I guess that's what I should expect for posting a link to it in another HN comment! :) These slides correspond to a workshop I conducted a week ago demonstrating the internals of Docker and how Docker containers can be run without using any of the Docker tools or runtime. Docker is a great tool, and I'm glad it's…
What about the entries in /dev? Is mknod not a thing anymore, or do I not need to have /dev entries in my container root filesystem?
Somewhat unrelated. Is there a way to ship a container image with just a "diff" of the default image. Say I build a container with ubuntu 14.04 + some packages installed with apt. I would like to be able to "export" the filesystem, but only the files that are not present in the base os image. The reason I would like this is that I would like to use docker (or systemd-nspawn) to run containers on an device that will n…