News for hackers. Stuff that matters.
Re:Show HN: CoreOS, a Linux distro for containers by alperakgun on Tuesday July 30, 2013 @02:30PM (#6128997)
for example.. if i m deploying a rails apps, how would coreos make it possible to install web servers, databases and rubygems? all through dockerfile descriptions? an app level getting started would be great..
Re:Show HN: CoreOS, a Linux distro for containers by philips on Tuesday July 30, 2013 @02:47PM (#6129128)
This is where we are going next; CoreOS is super young today though.

We want to build an environment where you run and manage all of those servers and databases inside of containers and via APIs. Or even better skip the APIs and just add nodes and have something like etcd help you configure it dynamically

But, we needed to get all of the foundations solid and that is where we are today.

Re:Show HN: CoreOS, a Linux distro for containers by dschiptsov on Wednesday July 31, 2013 @12:37AM (#6131933)
So, you are not encountered the dependency and version hell yet and just assumed that maintaining all the libs and tools a rails app is implicitly requires is a easy task?) Good luck, then.)
Re:Show HN: CoreOS, a Linux distro for containers by RickHull on Wednesday July 31, 2013 @02:37AM (#6132218)
No, that part is already solved. That's what containers do.

I believe philips is saying that CoreOS is still experimenting with and reifying exactly what the layer above containerized applications should be composed of and look like.

Re:Show HN: CoreOS, a Linux distro for containers by dschiptsov on Wednesday July 31, 2013 @04:52AM (#6132556)
So, basically, it looks like as if I move my /usr/local directory between hosts to be run under chroot, using aufs instead of tar.gz, lxc instead of chroot and some wrapper around ssh and scp? but with all that hype and memes? It looks like implementation of FreeBSD's jails with impoverished ports and fancy command-line tool. OK.

Update: what is really interesting is the amount of hype the Docker project created, having no fundamentally new ideas or technological advances, just well-written (we must admit) web pages full of buzzwords.

As a person who ran FreeBSD jail-based virtual hosting in production, I would say that disk and network I/O will be a bottleneck, because either interface does not scale well enough.)

Re:Show HN: CoreOS, a Linux distro for containers by Ixiaus on Wednesday July 31, 2013 @09:58AM (#6133667)
I've been running FreeBSD zfs backed jails for quite some time too (I still think FreeBSD is superior to Linux in many ways). What docker does that ezjails + zfs doesn't do is make it transportable. Sure you could write a script to bundle up your jail but Docker is making it possible to distribute an application orthogonally. Docker is also replete with tools for sharing containers, providing a container server (privately!), and many others...

On performance: containerization > virtualization. Containerization is also not just about performance (people are running it in virtualized environments) it's also about contained configurations.

Your tone is unnecessarily belligerent (I could be reading into what you wrote though).

Also - I know people who know people and are pushing for the Docker team to support containerizing FreeBSD jails too. Since the primary work horse right now for Docker is lxc, it should be possible to generalize it enough to include support for FreeBSD jails.

Docker does more than just "jail"; it does for jails what package managers did for programs.

Re:Show HN: CoreOS, a Linux distro for containers by dschiptsov on Thursday August 01, 2013 @09:21AM (#6140079)
I do not understand "orthogonality", sorry. I think in terms of ldd's output, and it tells me that nothing fundamentally new could be created. It either packages in /usr or stuff in /usr/local/ You might mount /usr as uniounfs - same for many jails, but you cannot undo dynamic linking, at least statically linked ruby is nonsense (but static linking sometimes is a good idea). I also cannot understand "containerization" why a snapshot created by tar is not a container? The assumption that you could reduce /lib is naive. Yes, /usr/lib could be reduced, but only by removing gnome stuff and some fancies.

I have tried to make minimalist but compatible system. It doesn't happen. Things like kerberos, sasl, ldap, pam messes everything up. I ended up with almost exactly the "minimum install". Paraphrasing a bit "dependencies! dependencies! dependencies!" and minimal install of Fedora or Ubuntu Server is almost optimal.

Re:Show HN: CoreOS, a Linux distro for containers by X4 on Thursday August 01, 2013 @11:36PM (#6145198)
If ZFS Snapshots were deployable to other machines in a network, then it would be really superior. Is that possible? By deploy I mean pushing snapshots into other machine's zpools, migrating them and lastly applying them. So that at the end you have a copy of the other server.

Well there's still no usable (web) gui for managing zfs (tell me what you want, but that IS wha is needed to make zfs more popular).

Would a minimal install of [your_server] into kvm give more rough performance than LXC+Docker?

One downside of Docker & LXC is that applications CAN breakout of the "jail" and affect the host machine. The docker guys told me about that fact and that they will work on that in the future.

After all that fizzbuzz, I'm not sure anymore, maybe chef/puppet/ansible or salt would be a much better solution than dealing with bits "manually". Because that would be the Model Driven Approach.

Re:Show HN: CoreOS, a Linux distro for containers by dschiptsov on Friday August 02, 2013 @12:18AM (#6145296)
Would a minimal install of [your_server] into kvm give more rough performance than LXC+Docker? The question is what for? Virtualization and production simply does not match.)

Close to so-called real life notion might be one like this: some guys managed to get funding for an mix of buzzwords they not fully understood themselves, especially an OS design. But after placing Minimum Viable Buzzwords website they got a lot of hype, so, magically, it became a "great idea" a "big thing" being absolutely nothing new and solving no real problems.

There is no problem with installation of packages or tarbals on the same system, through network, on multiple hosts, whatever. As long as it is the same version of the system. There is nothing to fix. It is optimal already and package managers and ports systems doing the job well enough, taking care of dependencies, security updates, restarts, etc.

All the buzz and hype is about people who do does not know and do not want to know how underlying system works, what are the basic ideas, etc. For such guys the promise of a simple interface (they can see it is simple on the site) which requires no thinking or understanding, is, of course, a piece of cake.

This is exactly how we have all the piles upon piles of Java crap. There is no need to think or understand and deployment is easy - just dumb all the shit in the same dir. Now we have all the mess and some smartases talking "JVM optimizations" but forgetting to mention, than a slight change in workload, leave alone the code, will make all their prior assumption invalid. OK, fuck it.

Re:Show HN: CoreOS, a Linux distro for containers by justincormack on Wednesday July 31, 2013 @08:47AM (#6133260)
SSD and 10Gb Ethernet are big changes...
Re:Show HN: CoreOS, a Linux distro for containers by cmelbye on Wednesday July 31, 2013 @03:38AM (#6132363)
Is it not an easy task? Install rvm and run "bundle" and you're pretty much done. Regardless, that's not necessarily part of the scope of this project as far as I can see. That's handled within the container which is managed by Docker and it's configuration system.
Re:Show HN: CoreOS, a Linux distro for containers by jon-wood on Tuesday July 30, 2013 @05:57PM (#6130318)
I just threw together a really simple proof of concept which uses a shell script to spin up a Docker instance running NGinx, and then register the port that instance is listening on with Etcd. Because it's quite so simple, here it is:

`INSTANCE=$(docker run jonwood/nginx-node) && curl http://127.0.0.1:4001/v1/keys/nginx-nodes/$INSTANCE -d $(docker port $INSTANCE 80)`

You'd then use Etcd's tree listing interface to grab the JSON fragments for each of those NGinx nodes, and configure Varnish or HAProxy or something to hit those backends.

Obviously this isn't anywhere near production ready (for example if one of your NGinx instances goes down there's nothing to remove it from the pool), but so far I'm impressed with what CoreOS is doing.

Re:Show HN: CoreOS, a Linux distro for containers by ideal0227 on Tuesday July 30, 2013 @06:49PM (#6130644)
"for example if one of your NGinx instances goes down there's nothing to remove it from the pool" For now, you can set up a node with TTL and update it. If the server goes down, the node will disappear. We are going to provide a client that will keep long connection with the server.
Re:Show HN: CoreOS, a Linux distro for containers by johnbellone on Wednesday July 31, 2013 @07:51AM (#6133008)
> (for example if one of your NGinx instances goes down there's nothing to remove it from the pool)

My plan to solve this was to use Doozer with a small daemon in each agent server which would keep some kind of registry of the services running on the machine. I think that could be relatively lightweight and with the ability to broadcast via watches there could be some kind of action attached to a node being removed and added.

Re:Show HN: CoreOS, a Linux distro for containers by FooBarWidget on Tuesday July 30, 2013 @02:33PM (#6129029)
From what I understand, it doesn't. You're expected to already have a container with a web server in it, and a container that already has a database in it. The web server container then uses the CoreOS service discovery feature to find out what IP address the database container listens that, and configures itself.

In other words, it does not replace Chef/Puppet. Maybe only for the configuration part, but not for the installation part. You may still want to use Chef/Puppet for creating the container in the first place.

Re:Show HN: CoreOS, a Linux distro for containers by justinsb on Tuesday July 30, 2013 @02:38PM (#6129067)
To my mind, the big idea here is that containers will self-configure. This is configuration _inside_ the container, rather than configuration from _outside_ the container (like Chef/Puppet etc).

This means that your Docker container doesn't need to run a Chef/Puppet/SSH configuration agent. It will need some sort of "discover my config and configure myself" process running, which would perform much the same role though.

In other words, the container is "smart" and self-assembles. If you need to add more webserver capacity (for scaling), you just launch more webserver containers; they will register themselves with the load balancer and attach to the database.

Of course, building these smart containers is non-trivial, so I'm eager to see some real-world examples.

Re:Show HN: CoreOS, a Linux distro for containers by FooBarWidget on Tuesday July 30, 2013 @02:52PM (#6129166)
What you're saying is exactly what I said in the first paragraph. Containers discover the config and configure themselves. But where do those containers come from in the first place and how to you build them? Where does that container, containing your in-house app, come from? That is where Chef/Puppet may come in.
Re:Show HN: CoreOS, a Linux distro for containers by justinsb on Tuesday July 30, 2013 @02:57PM (#6129205)
I was thinking that there would be a generic Rails container (like a Heroku buildpack), that reads the location of your Rails code from the configuration, downloads it, and runs it.

So, just like Heroku buildpacks, you can create your own, and you can even create one with your app baked in; but most people would end up using an off-the-shelf container.

But this is just my interpretation! Your approach may be better, and it doesn't look like CoreOS will care which way you want to do things!

Re:Show HN: CoreOS, a Linux distro for containers by adient on Tuesday July 30, 2013 @02:49PM (#6129143)
As mentioned, you would need "some sort of process" to config the host -- this is Puppet/Chef/etc. Replacing those is not trivial.

Also, not quite sure I understand config "inside vs outside" being the big idea. You can easily include Puppet manifests and have Puppet run in standalone mode from within the container with no outside access to config. That's not new.

Re:Show HN: CoreOS, a Linux distro for containers by chrissnell on Tuesday July 30, 2013 @05:34PM (#6130206)
Exactly. A container self-configuring by pulling it's config from an external service is pretty much the same as chef-client pulling down a configuration from the Chef server.

What I want from something like CoreOS is a stripped-down container host that will host stripped-down app containers. I want to package my app in the most-stripped-down fashion possible and deploy it on this stripped-down container host.

The idea of using Chef/Puppet to deploy an app onto a full-blown install of Ubuntu/CentOS/etc. seems like overkill. There's a lot of superfluous crap on that full install that consumes storage, memory, and CPU resources. Having a full OS also creates more attack vectors. If you were an attacker, would you rather root some Rails app on a full install of Ubuntu, complete with shells, compilers, etc., or a box with only the bare essentials required to run that Rails app?

I suppose that an argument for having a full-OS install is to make it easy for things like Chef/Puppet to update the server in situ. Stripped-down containers could make that unnecessary. Imagine an app container so small that it's easier to just blow away the container and create a new one with the freshest software.

Re:Show HN: CoreOS, a Linux distro for containers by s_baby on Tuesday July 30, 2013 @06:47PM (#6130628)
>What I want from something like CoreOS is a stripped-down container host that will host stripped-down app containers. I want to package my app in the most-stripped-down fashion possible and deploy it on this stripped-down container host.

If that's all you want then use Ubuntu Server.

Re:Show HN: CoreOS, a Linux distro for containers by chrissnell on Tuesday July 30, 2013 @09:59PM (#6131432)
That's not stripped down nearly enough for my tastes. I'm talking about the absolute bare minimum to make an app fully function.
Re:Show HN: CoreOS, a Linux distro for containers by justincormack on Wednesday July 31, 2013 @04:44AM (#6132539)
Working on a scripting interface to Linux designed so you can configure everything internally to your application (ie it can run as the init process) with no significant dependencies (you can statically link it)[1]. Its not finished yet, but you can configure network interfaces, routing etc. Needs some more examples, build scripts etc...

[1] https://github.com/justincormack/ljsyscall

Re:Show HN: CoreOS, a Linux distro for containers by sciurus on Wednesday July 31, 2013 @02:26PM (#6135826)
Re:Show HN: CoreOS, a Linux distro for containers by s_baby on Wednesday July 31, 2013 @02:12PM (#6135721)
The minimum install has ~4 processes running. You can only get so much more bare then that.
Re:Show HN: CoreOS, a Linux distro for containers by justinsb on Tuesday July 30, 2013 @02:54PM (#6129179)
Puppet could indeed be that process, and certainly replacing it isn't trivial. But I'm excited by the idea that we could replace it, by being able to rely on the configuration being directly available (provided by the OS). We'll have to see what gets created!
Re:Show HN: CoreOS, a Linux distro for containers by kekumu on Thursday August 01, 2013 @11:55AM (#6141171)
What's the advantage of it being built into the OS versus using chef or puppet? There's going to be some kind of process running to handle configuration no matter what. Docker also has Dockerfiles to handle configuration of containers. After seeing this article I looked into config management in Docker and containers and I'm having a hard time seeing why something like puppet/chef isn't the right solution.
Re:Show HN: CoreOS, a Linux distro for containers by dalore on Wednesday July 31, 2013 @05:47AM (#6132677)
You can design your containers/vm to self configure with puppet/chef. I have ec2 instance that you configure by telling it what role it is when you start it and then it has headless puppet scripts which configure it on boot.
Re:Show HN: CoreOS, a Linux distro for containers by justincormack on Tuesday July 30, 2013 @07:33PM (#6130846)
Indeed. It will happen. chef and puppet are replicating manual config. You need your app to configure its whole environment.
Re:Show HN: CoreOS, a Linux distro for containers by subway on Wednesday July 31, 2013 @09:11AM (#6133388)
If you're under the impression Puppet and Chef simply replicate a manual config, you're doing it wrong.

Look at concepts like Puppet's exported resources. The tools to accomplish service discovery have been around (and many of us have been using them) for year. I'm just excited to see the concept finally getting a bit more mindshare via Docker and now CoreOS.