Skip to content

Loading…

`no such file or directory` error after upgrading to 0.7.3 #3451

Closed
bamos opened this Issue · 4 comments

4 participants

@bamos

Hi, sorry if this isn't the right place to report this or if it's already been reported, but after I upgraded from Docker 0.7.2 to 0.7.3, a Dockerfile I'm working with fails to run apt-get update with the following error message.

docker-llvm-polly-pocl/llvm-3.4 [master] » docker build .
Uploading context 10.24 kB
Uploading context 
Step 1 : FROM ubuntu:12.04
Pulling repository ubuntu
8dbd9e392a96: Download complete  ---> 8dbd9e392a96
Step 2 : RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" >    /etc/apt/sources.list;  apt-get update
 ---> Running in 44442b1b1e93
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/universe amd64 Packages [6167 kB]
Get:2 http://archive.ubuntu.com precise/main i386 Packages [1641 kB]
Get:3 http://archive.ubuntu.com precise/universe i386 Packages [6180 kB]
Get:4 http://archive.ubuntu.com precise/main TranslationIndex [3706 B]
Get:5 http://archive.ubuntu.com precise/universe TranslationIndex [2922 B]
Get:6 http://archive.ubuntu.com precise/main Translation-en [893 kB]
Get:7 http://archive.ubuntu.com precise/universe Translation-en [4133 kB]
Fetched 19.0 MB in 51s (369 kB/s)

2014/01/04 14:55:36 no such file or directory

I'm running this in Arch Linux, and the Docker version for this was:

Docker version 0.7.3, build 8502ad4

After downgrading back to:

Docker version 0.7.2, build 28b162e

this error doesn't occur.

Let me know if I can provide more info. Thanks!

@Chris00

The same happens for me (also after an apt-get update).

@tianon
Collaborator

I'm seeing the same, but only on my devicemapper box, not on AUFS. The AUFS machine works flawlessly, but the exact same Dockerfile gives me no such file or directory. For me, it's not happening on the apt-get update itself, but after the entire RUN line (which also includes an apt-get install).

Here's a minimal Dockerfile that replicates this on devicemapper on my machine (simplified from what I was testing with when I ran into this originally):

FROM debian:sid
RUN apt-get update

Even more easily tested with echo -e 'FROM debian:sid\nRUN apt-get update' | docker build -rm -.

I also tested all these RUN commands instead of apt-get update, but they all build successfully just fine:

  • RUN echo hi
  • RUN touch /hello
  • RUN touch /var/run/something
  • RUN touch /var/lib/something (just testing a few paths that might be suspect, especially since /var/run is a symlink to /run)

Not sure what would be most useful to test next, but of course always happy to do so.

@bamos

Sorry, this is a duplicate issue of #3449

@crosbymichael

Closing as duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.