Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-24 14:57:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/mariadb] Release 10.10.3-debian-11-r3 (#24262)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-02-17 16:34:47 +01:00
committed by GitHub
parent c1a64a85cb
commit 774d2eeae5
3 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/mariadb/README.md
View File

@@ -137,7 +137,7 @@ docker run -it --rm \
bitnami/mariadb:latest mysql -h mariadb-server -u root
```
### Using Docker Compose
### Using a Docker Compose file
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the MariaDB server from your own custom application image which is identified in the following snippet by the service name `myapp`.
@@ -667,12 +667,12 @@ docker-compose up mariadb
* Backwards compatibility is not guaranteed when data is persisted using docker-compose. You can use the workaround below to overcome it:
```console
docker-compose down
$ docker-compose down
## Change the mount point
sed -i -e 's#mariadb_data:/bitnami#mariadb_data:/bitnami/mariadb#g' docker-compose.yml
## Pull the latest bitnami/mariadb image
docker pull bitnami/mariadb:latest
docker-compose up -d
$ docker pull bitnami/mariadb:latest
$ docker-compose up -d
```
### 10.1.28-r2 and 10.2.16-r2