From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.88.87] (unknown [36.80.217.41]) by gnuweeb.org (Postfix) with ESMTPSA id 072717E3A7; Sun, 17 Apr 2022 13:45:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1650203106; bh=uufuoIm1N5/BJ36zyAQSVcEd0VqXfab67fFoSrK0Hi0=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=cRwr6DGLtNJWTjjsruC2VLMaOwEmPQPHYQ4gHf/rGmIEs1LwjEpkWP1DtuxXPFlMH eOWd6P3nxfAxt55WtjFCsct6kEr2/3E+Iy8mM8GA8pcEF0BjaQkZJqU8IgdaEiYavv Pe2tZETKr2FjaAdMeW0Up6tB5nQSyUJByvOWLK2rVm/elBMVQ1jecYstDOs2y4E0Uy YUSvaYNDRAFOud8GSZFZPpYh5MDWPWCJTjTyF6h0KFH0b+HofELH4pt1BS8+dAbKuB 9mgyDCGXKD9BT+/PUdb8ivHWEJWeGwCFhI5D6Nhg7AIUND7vPAzUuyLH9gmuK3yKz7 rKJpGnjEy4yHw== Message-ID: Date: Sun, 17 Apr 2022 20:44:59 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-US To: Alviro Iskandar Setiawan Cc: GNU/Weeb Mailing List , Hazmi Alfarizqi , Hazmi Alfarizqi , Alviro Iskandar Setiawan References: <20220417125125.160068-1-ammarfaizi2@gnuweeb.org> <20220417125125.160068-3-ammarfaizi2@gnuweeb.org> From: Ammar Faizi Subject: Re: [PATCH server-a001 v1 2/2] Install MySQL server In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 4/17/22 8:34 PM, Alviro Iskandar Setiawan wrote: > On Sun, Apr 17, 2022 at 8:26 PM Ammar Faizi wrote: >> On 4/17/22 8:06 PM, Alviro Iskandar Setiawan wrote: > [...] >>> Also, it needs persistent storage, container is temporary, but our >>> database is permanent??? >> >> This is not a Dockerfile problem, it's a container problem. Which is >> done at `docker run`. So there is no relevance with mounting host's >> directory. >> >> The change is about Dockerfile. And we don't use a docker-compose.yml >> here. I don't see the need to involve that. Yes? No? Comment? > > Yes, but how do you tell other maintainers to mount the volume > correctly if you don't provide any mechanism in doing this? You should > tell us how to run it too! OK, I understand your concern. The database file that needs to be persistent lives in /var/lib/mysql. So: docker run -v $HOST_DIR_FOR_MYSQL_DATA:/var/lib/mysql ... something like that... I will provide something for it in the v2. Anyway, since the mysql user is managed by a database as well, this will be persistent across docker run too. Hence, it's the host responsibility to retain the mysql users. -- Ammar Faizi