Updating¶

MXProxy releases use semantic versioning.

For production deployments, avoid the latest tag. Pin MXProxy to a minor or patch version instead.

Choosing a version¶

To allow patch releases while staying on the same minor version:

image: malasaur/mxproxy:0.2

To pin your deployment to a specific release:

image: malasaur/mxproxy:0.2.0

Using a minor version such as 0.2 allows patch releases within that minor version. Using a patch version such as 0.2.0 pins the deployment to that specific release.

Always check the release notes before updating to a new minor version. Minor releases may contain breaking changes or require changes to your Docker Compose configuration.

Updating from 0.1 to 0.2¶

Add this to the mxproxy service in your compose.yaml:

extra_hosts:
  - "dockerhost:host-gateway"

For example:

services:
  mxproxy:
    image: malasaur/mxproxy:0.2.0
    # ...

    extra_hosts:
      - "dockerhost:host-gateway"

Then pull and recreate the container:

docker compose pull mxproxy
docker compose up -d --force-recreate mxproxy