I saw the blog announcement yesterday that docker is now supported, however, I think maybe it's broken.

I am running the latest kernel on Ubuntu 12.04.

I install docker using the instructions on the docker home page.

I then create a Dockerfile that says:

FROM ubuntu
RUN apt-get update

This then runs and does stuff, but errors with a "no such file or directory" error.

I checked with the docker guys on IRC, and they cannot reproduce this error. I also tested docker on a local ubuntu installation I have here, and it worked fine.

Suspect something isn't quite right with the linode kernel for this.

Follow up on this...

Following the instructions here works: http://coder1.com/articles/install-dock ... buntu-1204

So definitely looks like it's something with the stock linode kernel.

I deployed Ubuntu 13.04 (64-bit) on a new Linode, added the docker apt repo, apt-get install lxc-docker'd, and then ran a particular random Dockerfile from the index (https://index.docker.io/u/creack/cpuminer/). No problems were noted, launched fine. Kernel is 3.12.6-x86_64-linode36.

_________________

/* TODO: need to add signature to posts */

So, sounds like it's related to the kernel on 12.04?

I'm not sure that your test is valid.

There's specific commands that cause it to fail.

I attempted to set it up as you described, and it failed for me again.

To be very clear... your Dockerfile MUST contain the following:

FROM ubuntu
RUN apt-get update

that's all. it's the apt-get update command that fails.

If you do

FROM ubuntu
run apt-get install apache2

or something, it works. There are other commands that fail too, but this is the simplest test case.

The Dockerfile HoopyCat run does apt-get update as its first task. It'd be helpful if you actually pasted the output you got from your run, so that somebody could actually help. Otherwise we're just guessing at this point.

-Doug

Ok, here's a bunch of relevant output...

Here's my Dockerfile:

https://gist.github.com/jivadevoe/02703155a8611b2be563

Here's the output:

https://gist.github.com/jivadevoe/6970512987812f1ccbe5

Here's my docker version:

https://gist.github.com/jivadevoe/16bb8a10f29d6dce9e63

This is apparently an issue with Docker 0.7.3:

https://github.com/dotcloud/docker/issues/3451
https://github.com/dotcloud/docker/issues/3449

Here's the exact steps to a minimal reproduced environment:

1. create a linode with 12.04 ubuntu.
2. boot it
3. log in as root
4. install docker via: curl -s https://get.docker.io/ubuntu/ | sudo sh
5. create a Dockerfile with two lines:

     from ubuntu
     run apt-get update

6. run: docker build .

You will receive the following output:

Uploading context 20.48 kB
Uploading context 
Step 1 : FROM ubuntu
Pulling repository ubuntu
8dbd9e392a96: Download complete 
b750fe79269d: Download complete 
27cf78414709: Download complete 
 ---> 8dbd9e392a96
Step 2 : RUN apt-get update
 ---> Running in 70d4664776fb
Ign http://archive.ubuntu.com precise InRelease
Hit http://archive.ubuntu.com precise Release.gpg
Hit http://archive.ubuntu.com precise Release
Hit http://archive.ubuntu.com precise/main amd64 Packages
Get:1 http://archive.ubuntu.com precise/main i386 Packages [1641 kB]
Get:2 http://archive.ubuntu.com precise/main TranslationIndex [3706 B]
Get:3 http://archive.ubuntu.com precise/main Translation-en [893 kB]
Fetched 2537 kB in 3s (635 kB/s)

2014/01/05 06:16:41 no such file or directory

The "no such file or directory" is the failure. This causes the docker image to not be committed.

Note: this does not occur if you manually run "docker run ubuntu apt-get update" or whatever.

That's pretty much all there is to it guys.

Interesting and good to know, thanks. Strange though that it works after I switch to pv-grub and a different kernel.

Anyway, will downgrade to 0.7.1 then. Thanks.

confirmed, downgrading to 0.7.1 works

Thanks.