)]}'
{"doc/security.rst":[{"author":{"_account_id":16233,"name":"Mauricio Lima","email":"mauriciolimab@gmail.com","username":"limamauricio"},"change_message_id":"7290859e0bd0d2eae5f7adaf10a9a751a982a3f7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bab6814e_0cd8e852","side":"PARENT","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":8},"updated":"2016-05-18 15:42:55.000000000","message":"Maybe can be interesting not remove the \"Overview\" about SELinux. Can you add one note with it?","commit_id":"5ee2e6a87da7954cc73e52845ab62ef08e7b52a2"},{"author":{"_account_id":10419,"name":"Ryan Hallisey","email":"rhallise@redhat.com","username":"rhallisey"},"change_message_id":"622007f1d01da319989098c527c3e53b4297552f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bab6814e_ec9f645d","side":"PARENT","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":8},"in_reply_to":"bab6814e_0cd8e852","updated":"2016-05-18 15:57:07.000000000","message":"Done","commit_id":"5ee2e6a87da7954cc73e52845ab62ef08e7b52a2"},{"author":{"_account_id":11105,"name":"Swapnil Kulkarni","email":"coolsvap@gmail.com","username":"coolsvap"},"change_message_id":"ad37d676514a29c49245fdcbdf7c65830445f186","unresolved":false,"context_lines":[{"line_number":27,"context_line":"they were never recreated, leading to a scary state where you could lose access"},{"line_number":28,"context_line":"to your data if the wrong command was executed. The real answer to this problem"},{"line_number":29,"context_line":"came in Docker 1.9 with the introduction of named volumes. You could now"},{"line_number":30,"context_line":"address volumes directly by name removing the need for so called \"data"},{"line_number":31,"context_line":"containers\" all together."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Another solution to the persistent data issue is to use a host bind mount which"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab6814e_c787d20d","line":30,"range":{"start_line":30,"start_character":66,"end_line":30,"end_character":70},"updated":"2016-05-18 18:00:24.000000000","message":"maybe you can enclose in ** to highlight","commit_id":"ed2965d2c970155179e183bf5009a3ed45777f21"},{"author":{"_account_id":11105,"name":"Swapnil Kulkarni","email":"coolsvap@gmail.com","username":"coolsvap"},"change_message_id":"ad37d676514a29c49245fdcbdf7c65830445f186","unresolved":false,"context_lines":[{"line_number":31,"context_line":"containers\" all together."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Another solution to the persistent data issue is to use a host bind mount which"},{"line_number":34,"context_line":"involves making, for sake of example, host directory /var/lib/mysql available"},{"line_number":35,"context_line":"inside the container at /var/lib/mysql. This absolutely solves the problem of"},{"line_number":36,"context_line":"persistent data, but it introduces another security issue, permissions. With"},{"line_number":37,"context_line":"this host bind mount solution the data in /var/lib/mysql will be owned by the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab6814e_07cc3a88","line":34,"updated":"2016-05-18 18:00:24.000000000","message":"enclose in ``","commit_id":"ed2965d2c970155179e183bf5009a3ed45777f21"},{"author":{"_account_id":11105,"name":"Swapnil Kulkarni","email":"coolsvap@gmail.com","username":"coolsvap"},"change_message_id":"ad37d676514a29c49245fdcbdf7c65830445f186","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Another solution to the persistent data issue is to use a host bind mount which"},{"line_number":34,"context_line":"involves making, for sake of example, host directory /var/lib/mysql available"},{"line_number":35,"context_line":"inside the container at /var/lib/mysql. This absolutely solves the problem of"},{"line_number":36,"context_line":"persistent data, but it introduces another security issue, permissions. With"},{"line_number":37,"context_line":"this host bind mount solution the data in /var/lib/mysql will be owned by the"},{"line_number":38,"context_line":"mysql user in the container. Unfortunately, that mysql user in the container"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab6814e_c7b992eb","line":35,"range":{"start_line":35,"start_character":24,"end_line":35,"end_character":25},"updated":"2016-05-18 18:00:24.000000000","message":"ditto","commit_id":"ed2965d2c970155179e183bf5009a3ed45777f21"},{"author":{"_account_id":11105,"name":"Swapnil Kulkarni","email":"coolsvap@gmail.com","username":"coolsvap"},"change_message_id":"ad37d676514a29c49245fdcbdf7c65830445f186","unresolved":false,"context_lines":[{"line_number":34,"context_line":"involves making, for sake of example, host directory /var/lib/mysql available"},{"line_number":35,"context_line":"inside the container at /var/lib/mysql. This absolutely solves the problem of"},{"line_number":36,"context_line":"persistent data, but it introduces another security issue, permissions. With"},{"line_number":37,"context_line":"this host bind mount solution the data in /var/lib/mysql will be owned by the"},{"line_number":38,"context_line":"mysql user in the container. Unfortunately, that mysql user in the container"},{"line_number":39,"context_line":"could have any UID/GID and thats who will own the data outside the container"},{"line_number":40,"context_line":"introducing a potential security risk. Additionally, this method dirties the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab6814e_67c9c678","line":37,"updated":"2016-05-18 18:00:24.000000000","message":"ditto","commit_id":"ed2965d2c970155179e183bf5009a3ed45777f21"}]}