{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/18015","labels_url":"https://api.github.com/repos/docker/docker/issues/18015/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/18015/comments","events_url":"https://api.github.com/repos/docker/docker/issues/18015/events","html_url":"https://github.com/docker/docker/issues/18015","id":117152209,"number":18015,"title":"FIle system of container become read-only","user":{"login":"ivokotev","id":2969570,"avatar_url":"https://avatars.githubusercontent.com/u/2969570?v=3","gravatar_id":"","url":"https://api.github.com/users/ivokotev","html_url":"https://github.com/ivokotev","followers_url":"https://api.github.com/users/ivokotev/followers","following_url":"https://api.github.com/users/ivokotev/following{/other_user}","gists_url":"https://api.github.com/users/ivokotev/gists{/gist_id}","starred_url":"https://api.github.com/users/ivokotev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ivokotev/subscriptions","organizations_url":"https://api.github.com/users/ivokotev/orgs","repos_url":"https://api.github.com/users/ivokotev/repos","events_url":"https://api.github.com/users/ivokotev/events{/privacy}","received_events_url":"https://api.github.com/users/ivokotev/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-16T15:42:33Z","updated_at":"2015-11-16T15:42:34Z","closed_at":null,"body":"Hello friends,\r\n\r\nWe are having strange problem with file system of a container. We observed this issue in following running containers – opensuse, ubuntu (official) and sles12 all latest versions. Containers are run on VMWare VM host with SLES12.\r\n\r\nIssue is following: After we run the container /proc/mounts file shows that FS is read/write\r\n\r\ncat /proc/mounts \r\n… \r\n/dev/mapper/docker-254:5-1452-701284ae46bd92f54ddaa7914e9043ecb678c450f208dc1074fd2ba1a8865508 \r\n/ ext4 rw,relatime,discard,stripe=16,data=ordered \r\n0 0\r\n\r\nThen when I run an application that is using massively FS for writing some files on it, file system of the container become read-only and /proc/mounts shows following\r\n\r\ncat /proc/mounts \r\n… \r\n/dev/mapper/docker-254:5-1452-701284ae46bd92f54ddaa7914e9043ecb678c450f208dc1074fd2ba1a8865508 \r\n/ ext4 ro,relatime,discard,stripe=16,data=ordered \r\n0 0\r\n\r\nSimple way to reproduce the issue is execution of below script. It turns read/write FS mode \r\nto read-only.The idea of script is to simulate mass writing of files to FS of the container (in this case it creates 50000 text files each one having 100 lines) on file system. After a while FS of the container stands read-only and script stops working. By the way I observed that similar faire you can reproduce if you just echo some text many times (50000 ) on the console.\r\n\r\nHere is script source.\r\n\r\n#!/bin/bash \r\nfor (( c=1; c<=5000000; c++ )) \r\ndo \r\necho \"Some text $c\" >> outfile$(( c / 100 )).out \r\ndone"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/157073227","html_url":"https://github.com/docker/docker/issues/18015#issuecomment-157073227","issue_url":"https://api.github.com/repos/docker/docker/issues/18015","id":157073227,"user":{"login":"GordonTheTurtle","id":10620046,"avatar_url":"https://avatars.githubusercontent.com/u/10620046?v=3","gravatar_id":"","url":"https://api.github.com/users/GordonTheTurtle","html_url":"https://github.com/GordonTheTurtle","followers_url":"https://api.github.com/users/GordonTheTurtle/followers","following_url":"https://api.github.com/users/GordonTheTurtle/following{/other_user}","gists_url":"https://api.github.com/users/GordonTheTurtle/gists{/gist_id}","starred_url":"https://api.github.com/users/GordonTheTurtle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GordonTheTurtle/subscriptions","organizations_url":"https://api.github.com/users/GordonTheTurtle/orgs","repos_url":"https://api.github.com/users/GordonTheTurtle/repos","events_url":"https://api.github.com/users/GordonTheTurtle/events{/privacy}","received_events_url":"https://api.github.com/users/GordonTheTurtle/received_events","type":"User","site_admin":false},"created_at":"2015-11-16T15:42:34Z","updated_at":"2015-11-16T15:42:34Z","body":"Hi!\n\t\nPlease read this important information about creating issues.\n\nIf you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.\n\nIf you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.\n\nThis is an automated, informational response. \n\nThank you.\n\nFor more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues \n\n-----------------------------\nBUG REPORT INFORMATION\n-----------------------------\nUse the commands below to provide key information from your environment:\n\n`docker version`:\n`docker info`:\n`uname -a`:\n\nProvide additional environment details (AWS, VirtualBox, physical, etc.):\n\n\n\nList the steps to reproduce the issue:\n1.\n2.\n3.\n\n\nDescribe the results you received:\n\n\nDescribe the results you expected:\n\n\nProvide additional info you think is important:\n\n\n----------END REPORT ---------\n\n\n\n#ENEEDMOREINFO\n"}}