kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
LinuxServer-CI
rodzic
937228e3ed
commit
5e3ade8178
|
|
@ -1,6 +1,14 @@
|
|||
# linuxserver/mysql-workbench
|
||||
# [linuxserver/mysql-workbench](https://github.com/linuxserver/docker-mysql-workbench)
|
||||
|
||||
[](https://github.com/linuxserver/docker-mysql-workbench) [](https://github.com/linuxserver/docker-mysql-workbench/releases) [](https://github.com/linuxserver/docker-mysql-workbench/packages) [](https://gitlab.com/Linuxserver.io/docker-mysql-workbench/container_registry) [](https://microbadger.com/images/linuxserver/mysql-workbench) [](https://hub.docker.com/r/linuxserver/mysql-workbench) [](https://hub.docker.com/r/linuxserver/mysql-workbench) [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-mysql-workbench/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/mysql-workbench/latest/index.html)
|
||||
[](https://github.com/linuxserver/docker-mysql-workbench)
|
||||
[](https://github.com/linuxserver/docker-mysql-workbench/releases)
|
||||
[](https://github.com/linuxserver/docker-mysql-workbench/packages)
|
||||
[](https://gitlab.com/Linuxserver.io/docker-mysql-workbench/container_registry)
|
||||
[](https://microbadger.com/images/linuxserver/mysql-workbench "Get your own version badge on microbadger.com")
|
||||
[](https://hub.docker.com/r/linuxserver/mysql-workbench)
|
||||
[](https://hub.docker.com/r/linuxserver/mysql-workbench)
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-mysql-workbench/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/mysql-workbench/latest/index.html)
|
||||
|
||||
[MySQL Workbench](https://www.mysql.com/products/workbench/) is a unified visual tool for database architects, developers, and DBAs. MySQL Workbench provides data modeling, SQL development, and comprehensive administration tools for server configuration, user administration, backup, and much more.
|
||||
|
||||
|
|
@ -13,16 +21,17 @@ Simply pulling `linuxserver/mysql-workbench` should retrieve the correct image f
|
|||
The architectures supported by this image are:
|
||||
|
||||
| Architecture | Tag |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| x86-64 | latest |
|
||||
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker
|
||||
|
||||
```text
|
||||
```
|
||||
docker create \
|
||||
--name=mysql-workbench \
|
||||
-e PUID=1000 \
|
||||
|
|
@ -35,6 +44,7 @@ docker create \
|
|||
linuxserver/mysql-workbench
|
||||
```
|
||||
|
||||
|
||||
### docker-compose
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
|
@ -61,41 +71,42 @@ services:
|
|||
|
||||
## Parameters
|
||||
|
||||
Docker images are configured using parameters passed at runtime \(such as those above\). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
||||
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
||||
|
||||
### Ports \(`-p`\)
|
||||
### Ports (`-p`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `3000` | Mysql Workbench desktop gui. |
|
||||
|
||||
### Environment Variables \(`-e`\)
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
|
||||
|
||||
### Volume Mappings \(`-v`\)
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `/config` | Users home directory in the container, stores program settings. |
|
||||
|
||||
#### Miscellaneous Options
|
||||
|
||||
#### Miscellaneous Options
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| :-----: | --- |
|
||||
| `--cap-add=` | Required for keyring functionality |
|
||||
|
||||
## Environment variables from files \(Docker secrets\)
|
||||
## Environment variables from files (Docker secrets)
|
||||
|
||||
You can set any environment variable from a file by using a special prepend `FILE__`.
|
||||
|
||||
As an example:
|
||||
|
||||
```text
|
||||
```
|
||||
-e FILE__PASSWORD=/run/secrets/mysecretpassword
|
||||
```
|
||||
|
||||
|
|
@ -103,17 +114,19 @@ Will set the environment variable `PASSWORD` based on the contents of the `/run/
|
|||
|
||||
## Umask for running applications
|
||||
|
||||
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
|
||||
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
|
||||
|
||||
## User / Group Identifiers
|
||||
|
||||
When using volumes \(`-v` flags\), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||
|
||||
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
||||
|
||||
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
||||
|
||||
```text
|
||||
```
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
|
@ -122,17 +135,18 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
|
|||
|
||||
The application can be accessed at:
|
||||
|
||||
* [http://yourhost:3000/](http://yourhost:3000/)
|
||||
* http://yourhost:3000/
|
||||
|
||||
By default the user/pass is abc/abc, if you change your password or want to login manually to the GUI session for any reason use the following link:
|
||||
|
||||
* [http://yourhost:3000/?login=true](http://yourhost:3000/?login=true)
|
||||
* http://yourhost:3000/?login=true
|
||||
|
||||
|
||||
## Docker Mods
|
||||
[](https://mods.linuxserver.io/?mod=mysql-workbench "view available mods for this container.")
|
||||
|
||||
[](https://mods.linuxserver.io/?mod=mysql-workbench)
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
|
||||
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image \(if any\) can be accessed via the dynamic badge above.
|
||||
|
||||
## Support Info
|
||||
|
||||
|
|
@ -148,4 +162,3 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
|
|||
## Versions
|
||||
|
||||
* **26.03.20:** - Initial release.
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue