Skip to content

Loading…

Dockerfile build fail on devicemapper #3449

Closed
rsampaio opened this Issue · 17 comments

9 participants

@rsampaio

On Arch linux, docker version 0.7.3 and 0.7.2 with the following simple Dockerfile:

FROM ubuntu
RUN apt-get update
RUN apt-get install ssh-server

docker build -rm -t test .

Fails with the following message:

2014/01/04 04:00:01 no such file or directory

docker debug log says:

[debug] image.go:92 Start untar layer
[debug] archive.go:82 [tar autodetect] n: 10
[debug] diff.go:151 unhandled type 83

Downgrading to 0.7.1 works

Client version: 0.7.1
Go version (client): go1.2
Git commit (client): e39d35d

@crigor

Jiva_ on IRC reported the same problem on a linode VM. Ubuntu 12.04. Devicemapper

FROM ubuntu
RUN apt-get update

2014/01/04 07:13:34 no such file or directory

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

root@li419-160:~/foo# docker version
Client version: 0.7.3
Go version (client): go1.2
Git commit (client): 8502ad4
Server version: 0.7.3
Git commit (server): 8502ad4
Go version (server): go1.2
Last stable version: 0.7.3

I tested this on my linode VM too. Downgrading to 0.7.1 fixed the issue.

@akerl

This appear to work for me, but may be because I tried with 0.7.2 and then with 0.7.3?

https://gist.github.com/akerl/8256651

I'm about to try a fresh deployment with 0.7.3 from the start, will update when that's done

root@localhost:/opt/docker-recipes/nginx-flask# docker version
Client version: 0.7.3
Go version (client): go1.2
Git commit (client): 8502ad4
Server version: 0.7.3
Git commit (server): 8502ad4
Go version (server): go1.2
Last stable version: 0.7.3
@akerl

Confirmed the bug occurs on a fresh 0.7.3 deployment:

https://gist.github.com/akerl/8256761

root@localhost:/opt/docker-recipes/nginx-flask# docker version
Client version: 0.7.3
Go version (client): go1.2
Git commit (client): 8502ad4
Server version: 0.7.3
Git commit (server): 8502ad4
Go version (server): go1.2
Last stable version: 0.7.3
@crosbymichael

@akerl are you running devicemapper as well?

@crosbymichael

I just ran the integration tests with devicemapper and they passed on my system. Will look into the tar code.

@akerl
@yasuoza

0.7.3 fresh install makes no such file or directory error. docker info and version are following:

vagrant@docker-base:~$ sudo docker info
Containers: 0
Images: 0
Driver: devicemapper
 Pool Name: docker-8:1-264253-pool
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 291.5 Mb
 Data Space Total: 102400.0 Mb
 Metadata Space Used: 0.7 Mb
 Metadata Space Total: 2048.0 Mb
WARNING: No swap limit support

vagrant@docker-base:~$ sudo docker version
Client version: 0.7.3
Go version (client): go1.2
Git commit (client): 8502ad4
Server version: 0.7.3
Git commit (server): 8502ad4
Go version (server): go1.2
Last stable version: 0.7.3

But, 0.7.2 -> 0.7.3 upgrade does not make the error.

@petrosagg

Same bug here, downgrading to 0.7.1 fixes the issue

@unclejack
Collaborator

+1
I'm still hitting this with the latest master.

@Chris00

FWIW, 0.7.2 also works for me.

@oscarrenalias

I can confirm the same issue with 0.7.3 using the .deb package in Ubuntu 13.10 with devicemapper, while downgrading to 0.7.2 fixed it.

@unclejack unclejack referenced this issue from a commit in unclejack/docker
@unclejack unclejack Revert "Add -S option to tar for efficient sparse file handling"
This reverts commit 733bf5d.

This is needed to fix "no such file" errors `docker build` errors for
devicemapper.

This fixes issue #3449.
4295899
@unclejack unclejack referenced this issue from a commit in unclejack/docker
@unclejack unclejack Revert "Add -S option to tar for efficient sparse file handling"
This reverts commit 733bf5d.

This is needed to fix "no such file" errors `docker build` errors for
devicemapper.

This fixes issue #3449.

Docker-DCO-1.0-Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com> (github: unclejack)
d003cfe
@unclejack
Collaborator

@rsampaio @akerl @crigor @oscarrenalias @petrosagg @Chris00 @yasuoza Could you try out Docker 0.7.4 with devicemapper to check if you're still running into this problem, please?

@oscarrenalias

I can confirm that 0.7.4 fixes the problem for me using the Dockerfile that didn't work with 0.7.3.

@yasuoza

0.7.4 with devicemapper works fine to me. Thank you!

@unclejack
Collaborator

@oscarrenalias @yasuoza Thank you for confirming that the problem is fixed for you. Cheers!

@unclejack unclejack closed this
@Chris00
@crigor

0.7.4 works for me. Thanks @unclejack.

(Github notifications should not skip my inbox :)

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.