Merge pull request #502 from infosiftr/sql

Add encoding hints for mysql, mariadb, and percona
This commit is contained in:
yosifkit 2016-03-14 16:20:46 -07:00
commit 3f8888462d
3 changed files with 42 additions and 0 deletions

View File

@ -72,6 +72,20 @@ Note that users on host systems with SELinux enabled may see issues with this. T
$ chcon -Rt svirt_sandbox_file_t /my/custom
```
### Configuration without a `cnf` file
Many configuration options can be passed as flags to `mysqld`. This will give you the flexibility to customize the container without needing a `cnf` file. For example, if you want to change the default encoding and collation for all tables to use UTF-8 (`utf8mb4`) just run the following:
```console
$ docker run --name some-%%REPO%% -e MYSQL_ROOT_PASSWORD=my-secret-pw -d %%REPO%%:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
```
If you would like to see a complete list of available options, just run:
```console
$ docker run -it --rm %%REPO%%:tag --verbose --help
```
## Environment Variables
When you start the `%%REPO%%` image, you can adjust the configuration of the MariaDB instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.

View File

@ -70,6 +70,20 @@ Note that users on host systems with SELinux enabled may see issues with this. T
$ chcon -Rt svirt_sandbox_file_t /my/custom
```
### Configuration without a `cnf` file
Many configuration options can be passed as flags to `mysqld`. This will give you the flexibility to customize the container without needing a `cnf` file. For example, if you want to change the default encoding and collation for all tables to use UTF-8 (`utf8mb4`) just run the following:
```console
$ docker run --name some-%%REPO%% -e MYSQL_ROOT_PASSWORD=my-secret-pw -d %%REPO%%:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
```
If you would like to see a complete list of available options, just run:
```console
$ docker run -it --rm %%REPO%%:tag --verbose --help
```
## Environment Variables
When you start the `%%REPO%%` image, you can adjust the configuration of the MySQL instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.

View File

@ -72,6 +72,20 @@ Note that users on host systems with SELinux enabled may see issues with this. T
$ chcon -Rt svirt_sandbox_file_t /my/custom
```
### Configuration without a `cnf` file
Many configuration options can be passed as flags to `mysqld`. This will give you the flexibility to customize the container without needing a `cnf` file. For example, if you want to change the default encoding and collation for all tables to use UTF-8 (`utf8mb4`) just run the following:
```console
$ docker run --name some-%%REPO%% -e MYSQL_ROOT_PASSWORD=my-secret-pw -d %%REPO%%:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
```
If you would like to see a complete list of available options, just run:
```console
$ docker run -it --rm %%REPO%%:tag --verbose --help
```
## Environment Variables
When you start the `%%REPO%%` image, you can adjust the configuration of the Percona instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.