Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6zKz-0004wX-7f for pgsql-admin@arkaria.postgresql.org; Thu, 21 Mar 2019 15:10:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6zKx-000289-O2 for pgsql-admin@arkaria.postgresql.org; Thu, 21 Mar 2019 15:10:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6zKx-00027z-Am for pgsql-admin@lists.postgresql.org; Thu, 21 Mar 2019 15:10:31 +0000 Received: from st43p00im-zteg10073401.me.com ([17.58.63.181]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6zKu-0000IF-CB for pgsql-admin@lists.postgresql.org; Thu, 21 Mar 2019 15:10:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1553181027; bh=V2ZZlzgjdLpO2MqJXEUhLT7g9TrQmwVFbVLdCUeBW/0=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=Edw6kcre86WHuhOLyr0ao2kkQ0ZBZiobkg49QdiZ7DtGEPscWtUv3M3kKjfU9C1jC KmfFQxiLsVAjFmmyhXrUWlGl6yKQMWB3eYCUv1mXn7eUKPdIT6wfkf9fwP22oQDOlC 1nzC+9BB0YqnvLkxoG/0dOn3vXeJzsrtGCFWp2oRCuI0VpN1CBTRaZdIdwArOeBz4R GasMS6vg2QiSKFA70KpeNjG00anj6s52h+7VcA7vVCtfRYgblm6bnGDz/H9r3aV95p ZN185xiyFfodtIkHYJDt53wBq/6xPa0wxUfygy7IXgjmX5WkXkq4v7j8DOki/RdnDq WbQM+d72z/IMg== Received: from [192.168.1.137] (cpe-184-152-57-116.nyc.res.rr.com [184.152.57.116]) by st43p00im-zteg10073401.me.com (Postfix) with ESMTPSA id D85DA5E00D6; Thu, 21 Mar 2019 15:10:26 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Running postgresql databases in Docker From: Evan Bauer In-Reply-To: Date: Thu, 21 Mar 2019 11:10:25 -0400 Cc: pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <704D13AE-1174-4F32-9D71-C5C376B97582@mac.com> References: To: M Jane X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-21_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1812120000 definitions=main-1903210108 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Docker can certainly work, but for any kind of production application = don=E2=80=99t keep the storage inside of the containers. Take a look at = the approach Crunchy Data (crunchydata.com) has done in their Kubernetes = orchestrator for PostgreSQL clusters as a solid implementation example. = Sarah Conway good a good presentation at PostgresOpn SV last September, = it may be online somewhere.=20 Cheers, - Evan Evan Bauer eb@evanbauer.com +1 646 641 2973 Skype: evanbauer > On Mar 21, 2019, at 04:28, M Jane wrote: >=20 > Hi everyone, > I am investigating using Docker for our Postgresql databases and I = have rad a lot of oppinions on forums. > The main thing that comes up is how to persist the data, and that it = is not advised to run production with docker. > I would like your advise. > What is your experience with Docker and databases? > What is the best practise to do this? > Your help is much appreciated. > Thanks in advance. > regards, > Marian