{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/20560","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/20560/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/20560/comments","events_url":"https://api.github.com/repos/docker/docker/issues/20560/events","html_url":"https://github.com/docker/docker/issues/20560","id":135231333,"number":20560,"title":"Unable to remove filesystem - device or resource busy","user":{"login":"ceecko","id":8225242,"avatar_url":"https://avatars.githubusercontent.com/u/8225242?v=3","gravatar_id":"","url":"https://api.github.com/users/ceecko","html_url":"https://github.com/ceecko","followers_url":"https://api.github.com/users/ceecko/followers","following_url":"https://api.github.com/users/ceecko/following{/other_user}","gists_url":"https://api.github.com/users/ceecko/gists{/gist_id}","starred_url":"https://api.github.com/users/ceecko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ceecko/subscriptions","organizations_url":"https://api.github.com/users/ceecko/orgs","repos_url":"https://api.github.com/users/ceecko/repos","events_url":"https://api.github.com/users/ceecko/events{/privacy}","received_events_url":"https://api.github.com/users/ceecko/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-02-21T17:32:45Z","updated_at":"2016-10-18T16:04:54Z","closed_at":"2016-02-22T13:35:33Z","body":"Hi,\r\n\r\nI started to experience the following error:\r\n```\r\nUnable to remove filesystem for bda61d0446fa7f54681b677641334407e04f8bb40d9b76540368987fbfe3937e: remove /var/lib/docker/containers/bda61d0446fa7f54681b677641334407e04f8bb40d9b76540368987fbfe3937e/shm: device or resource busy\r\n```\r\n\r\nThe error is thrown after `docker stop container` during `docker rm container`. The stop and rm action is performed via remote api.\r\n\r\nThis started after I added a custom bridge network with `docker network create network-name` but I'm not sure if it's connected.\r\n\r\nThe container stays in `dead` state until `docker rm -f container`\r\nWhat other information can I provide?\r\n\r\nDocker info\r\n```\r\nContainers: 91\r\n Running: 85\r\n Paused: 0\r\n Stopped: 6\r\nImages: 9\r\nServer Version: 1.10.1\r\nStorage Driver: devicemapper\r\n Pool Name: docker_pool-docker\r\n Pool Blocksize: 65.54 kB\r\n Base Device Size: 107.4 GB\r\n Backing Filesystem: ext4\r\n Data file:\r\n Metadata file:\r\n Data Space Used: 9.644 GB\r\n Data Space Total: 26.7 GB\r\n Data Space Available: 17.06 GB\r\n Metadata Space Used: 17.73 MB\r\n Metadata Space Total: 121.6 MB\r\n Metadata Space Available: 103.9 MB\r\n Udev Sync Supported: true\r\n Deferred Removal Enabled: false\r\n Deferred Deletion Enabled: false\r\n Deferred Deleted Device Count: 0\r\n Library Version: 1.02.107-RHEL7 (2015-12-01)\r\nExecution Driver: native-0.2\r\nLogging Driver: journald\r\nPlugins:\r\n Volume: local\r\n Network: bridge null host\r\nKernel Version: 3.10.0-327.10.1.el7.x86_64\r\nOperating System: CentOS Linux 7 (Core)\r\nOSType: linux\r\nArchitecture: x86_64\r\nCPUs: 2\r\nTotal Memory: 7.389 GiB\r\nName: ip-172-31-25-29.eu-west-1.compute.internal\r\nID: ZUTN:S7TL:6JRZ:HG52:LDLZ:VR5Q:RWVV:IP7E:HOQ4:R55X:Z7AI:P63R\r\nWARNING: bridge-nf-call-iptables is disabled\r\nWARNING: bridge-nf-call-ip6tables is disabled\r\n```\r\n\r\nDocker version\r\n```\r\ndocker version\r\nClient:\r\n Version:      1.10.1\r\n API version:  1.22\r\n Go version:   go1.5.3\r\n Git commit:   9e83765\r\n Built:        Thu Feb 11 19:18:46 2016\r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      1.10.1\r\n API version:  1.22\r\n Go version:   go1.5.3\r\n Git commit:   9e83765\r\n Built:        Thu Feb 11 19:18:46 2016\r\n OS/Arch:      linux/amd64\r\n```"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/254555866","html_url":"https://github.com/docker/docker/issues/20560#issuecomment-254555866","issue_url":"https://api.github.com/repos/docker/docker/issues/20560","id":254555866,"user":{"login":"buckett","id":5921,"avatar_url":"https://avatars.githubusercontent.com/u/5921?v=3","gravatar_id":"","url":"https://api.github.com/users/buckett","html_url":"https://github.com/buckett","followers_url":"https://api.github.com/users/buckett/followers","following_url":"https://api.github.com/users/buckett/following{/other_user}","gists_url":"https://api.github.com/users/buckett/gists{/gist_id}","starred_url":"https://api.github.com/users/buckett/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/buckett/subscriptions","organizations_url":"https://api.github.com/users/buckett/orgs","repos_url":"https://api.github.com/users/buckett/repos","events_url":"https://api.github.com/users/buckett/events{/privacy}","received_events_url":"https://api.github.com/users/buckett/received_events","type":"User","site_admin":false},"created_at":"2016-10-18T16:04:54Z","updated_at":"2016-10-18T16:04:54Z","body":"@thaJeztah I've just seen this today:\r\n\r\n````\r\n$ docker rm 299f70df1c318164b256a8f6d2b84c46a67f3b44fc0dc329db8457b96ffe6550\r\nError response from daemon: Unable to remove filesystem for 299f70df1c318164b256a8f6d2b84c46a67f3b44fc0dc329db8457b96ffe6550: remove /var/lib/docker/containers/299f70df1c318164b256a8f6d2b84c46a67f3b44fc0dc329db8457b96ffe6550/shm: device or resource busy\r\n\r\n$ docker version\r\nClient:\r\n Version:      1.12.0\r\n API version:  1.24\r\n Go version:   go1.6.3\r\n Git commit:   8eab29e\r\n Built:        Thu Jul 28 23:54:00 2016\r\n OS/Arch:      darwin/amd64\r\n\r\nServer:\r\n Version:      1.12.2\r\n API version:  1.24\r\n Go version:   go1.6.3\r\n Git commit:   bb80604\r\n Built:        Tue Oct 11 18:19:35 2016\r\n OS/Arch:      linux/amd64\r\n````"}}
{"actor":{"display_login":"buckett"}}