Hacker News Reader

Comment by MatthewPhillips | Hacker News Reader

It's unfortunate that it requires a 3.8 kernel, as getting those to work on most machines has been in my experience rather difficult. I had to downgrade back to 3.2 on a Ubuntu server because it wouldn't boot with 3.8. I was able to get it to work on a DigitalOcean fresh VM, but unless I want to migrate everything to a fresh VM, which I don't, I don't see myself using it for a while.

View on HN

Broader compatibility (including reducing kernel dependency) is a major part of this push. There are a number of workarounds today (e.g. patching the kernel, deploying as VM) which are discussed on http://www.docker.io/gettingstarted/ But, obviously, such workarounds aren't practical in every environment.

Just an FYI - tryrethink.info and my blog (nick.stinemat.es) are both running on 3.2.0-48. While it is not the recommended configuration, I haven't had any kernel related issues.

FYI - memcachedasaservice.com:

  ubuntu:~$ uname -a
  Linux ip-10-85-147-7 3.2.0-36-virtual #57-Ubuntu SMP Tue Jan 8 22:04:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:	Ubuntu
  Description:	Ubuntu 12.04.1 LTS
  Release:	12.04
  Codename:	precise

Pretty stable so far (200 docker containers running on the box)

Sounds like your problem is not with the 3.8+ kernel but with your choice of distributions that do not support it properly.

Given that Docker currently requires AUFS, Ubuntu is the distro of choice, so it's a problem.

Aufs works fine on Debian as well?

Reply on news.ycombinator.com