Bug 1096076 - ADDing file to symlinked /bin hangs, docker process spinning at 100 % CPU
Summary: ADDing file to symlinked /bin hangs, docker process spinning at 100 % CPU
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: docker-io
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Heon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-09 08:22 UTC by Jan Pazdziora
Modified: 2015-01-04 21:53 UTC (History)
11 users (show)

Fixed In Version: docker-io-1.0.0-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-25 11:37:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Pazdziora 2014-05-09 08:22:38 UTC
Description of problem:

On Fedora 20, /bin is a symlink to usr/bin. When Dockerfile tries to ADD file to /bin, the process will hang, with the daemon spinning at 100 % CPU.

Version-Release number of selected component (if applicable):

docker-io-0.11.1-1.fc20.x86_64
Seen on 0.10* as well.

How reproducible:

Deterministic.

Steps to Reproduce:
1. echo test > testfile
2. have Dockerfile with
    FROM fedora:20
    ADD testfile /bin/testfile
3. run docker build -t test-symlink .

Actual results:

Uploading context 4.608 kB
Uploading context 
Step 0 : FROM fedora:20
 ---> b7de3133ff98
Step 1 : ADD testfile /bin/testfile

and that's it, top in another terminal shows 

Expected results:

# docker build -t test-symlink .
Uploading context 5.632 kB
Uploading context 
Step 0 : FROM fedora:20
 ---> b7de3133ff98
Step 1 : ADD testfile /bin/testfile
 ---> 6fb52b6363f7
Removing intermediate container 11254a256eb7
Successfully built 6fb52b6363f7
#

Additional info:

ADD to /usr/bin/testfile works.

Comment 1 Jan Pazdziora 2014-05-09 08:59:59 UTC
I should add: it is a regression against docker-io-0.9 so it has the potential of hitting people who were happily using ADD to /bin in the past.

Comment 2 Daniel Walsh 2014-05-28 16:25:52 UTC
Could you check if this is fixed in docker-io-0.11.1-2.fc20

Comment 3 Jan Pazdziora 2014-05-29 07:46:28 UTC
(In reply to Daniel Walsh from comment #2)
> Could you check if this is fixed in docker-io-0.11.1-2.fc20

I don't see this fixed with docker-io-0.11.1-3.fc20.x86_64.

Comment 4 Matthew Heon 2014-06-06 12:54:30 UTC
Issue is fixed in upstream - build of their Git master does not have this issue. I'll identify the patch so we can carry it until the next upstream release.

Comment 5 Daniel Walsh 2014-06-06 13:05:26 UTC
Well we should be rebasing as soon as they release.  Rather then carry the patch.

Comment 6 Matthew Heon 2014-06-11 12:51:04 UTC
This is fixed in docker-io-1.0.0-1, which just made it into updates-testing.

Comment 7 Jan Pazdziora 2014-06-25 11:37:17 UTC
I confirm the issue fixed.


Note You need to log in before you can comment on or make changes to this bug.