Docker MySQL Shell Images

This repository contains Dockerfiles for MySQL Shell in two different series:

• Innovation Series (9.2.x) - Latest features (Dockerfile)
• LTS Series (8.4.x) - Long Term Support (Dockerfile)

Both images are based on Debian 12 (slim) for minimal image size.

Available Tags

Innovation Series (Dockerfile)

• snickerjp/docker-mysql-shell:9.2 - Innovation series with specific version
• snickerjp/docker-mysql-shell:Innovation - Latest Innovation series build

LTS Series (Dockerfile)

• snickerjp/docker-mysql-shell:8.4 - LTS series with specific version
• snickerjp/docker-mysql-shell:LTS - Latest LTS series build
• snickerjp/docker-mysql-shell:latest - Same as LTS series

Building the Images

Innovation Series (9.2.x) (Dockerfile)

cd docker/innovation
docker build -t snickerjp/docker-mysql-shell:9.2 .

LTS Series (8.4.x) (Dockerfile)

cd docker/lts
docker build -t snickerjp/docker-mysql-shell:8.4 .

Usage

Run MySQL Shell container:

# Innovation Series
docker run -it snickerjp/docker-mysql-shell:9.2
# or
docker run -it snickerjp/docker-mysql-shell:Innovation

# LTS Series
docker run -it snickerjp/docker-mysql-shell:8.4
# or
docker run -it snickerjp/docker-mysql-shell:LTS
# or
docker run -it snickerjp/docker-mysql-shell:latest

To connect to a MySQL Server:

# Innovation Series
docker run -it snickerjp/docker-mysql-shell:9.2 --uri mysql://user:pass@host:port/schema
# or using Innovation tag
docker run -it snickerjp/docker-mysql-shell:Innovation --uri mysql://user:pass@host:port/schema

# LTS Series
docker run -it snickerjp/docker-mysql-shell:8.4 --uri mysql://user:pass@host:port/schema
# or using LTS tag
docker run -it snickerjp/docker-mysql-shell:LTS --uri mysql://user:pass@host:port/schema

Development Workflow

Branch Strategy

• feat-*: Feature branches for new features and improvements
• develop: Integration branch for feature branches
• main: Release branch

Pull Request Process

1. Create a new feature branch from develop:

git checkout develop
git pull origin develop
git checkout -b feat-your-feature-name

2. Make your changes and create a PR to develop
3. After PR is merged to develop, it will be included in the next release PR
4. Release PRs are automatically created from develop to main using git-pr-release

Protected Branches

• develop: Requires PR review and successful status checks
• main: Protected release branch, only accepts PRs from develop