From 57deb98b592516cbb4d912e6131690001d67eef8 Mon Sep 17 00:00:00 2001
From: STAM <stamepicmorg@users.noreply.github.com>
Date: Tue, 18 Sep 2018 22:39:28 +0300
Subject: [PATCH] Update README.md

---
 bitbucket/latest/README.md | 12 ++----------
 1 file changed, 2 insertions(+), 10 deletions(-)

diff --git a/bitbucket/latest/README.md b/bitbucket/latest/README.md
index aaf5bc7de..277f1dcc7 100644
--- a/bitbucket/latest/README.md
+++ b/bitbucket/latest/README.md
@@ -7,21 +7,13 @@ Learn more about Bitbucket Server: <https://www.atlassian.com/software/bitbucket
 # Overview
 
 This Docker container makes it easy to get an instance of Bitbucket up and running.
-
-** We strongly recommend you run this image using a specific version tag instead of latest. This is because the image referenced by the latest tag changes often and we cannot guarantee that it will be backwards compatible. **
+ 
 
 # Quick Start
 
 For the `BITBUCKET_HOME` directory that is used to store the repository data
 (amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9. 
-
-## For Bitbucket 4.12+
-
-In Bitbucket 4.12 and later versions, volume permission is managed by entry scripts. To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
-
-    $> docker volume create --name bitbucketVolume
-    $> docker run -v bitbucketVolume:/var/atlassian/application-data/bitbucket --name="bitbucket" -d -p 7990:7990 -p 7999:7999 epicmorg/bitbucket
-
+ 
 ## For other versions
 
 Set permissions for the data directory so that the runuser can write to it: