Bug 1089992

Summary: docker run hangs when system is stressed
Product: [Fedora] Fedora Reporter: Lukáš Doktor <ldoktor>
Component: docker-ioAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: admiller, golang-updates, jkeck, lsm5, mattdm, mgoldman, s, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-22 13:47:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukáš Doktor 2014-04-22 10:43:34 UTC 
Description of problem:
When I use `docker run` and the system is under great stress, even when the stress finishes, the `docker run` command never starts/finishes.

Version-Release number of selected component (if applicable):
docker-io-0.10.0-2.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
1. start stress (on my laptop: `stress -c 1 -i 1 -m 1 -d 1 -t 60`)
2. use `docker -D run -i -t fedora bash`
3. wait for infinity....

Actual results:
docker is not started, output of /var/log/messages is:
Apr 22 12:17:51 t530 docker: 2014/04/22 12:17:51 POST /v1.10/containers/create
Apr 22 12:17:51 t530 docker: [/home/medic/Work/Projekty/Docker/root|0e364d3a] +job create()
...
never finishes, even after the stress command finishes (60s). I can then execute other docker commands, but the one started during stress execution never finishes and is not logged in `docker events` nor `docker ps -a`

Expected results:
New container is created (at least when the stress finishes)
Comment 1 Lukáš Doktor 2014-04-22 13:47:09 UTC 
Hi guys, sorry, my fault. It was due of hanged NFS... So this is not a docker bug...