License activation in Docker

You can activate a WProofreader license in two ways:

• during image build (recommended)

• on container startup (trial-friendly)

Option 1 (recommended): Activate during image build

Pass the license ticket as a build argument:

• --build-arg WPR_LICENSE_TICKET_ID=<license_ticket_id>

This persists the activated license into the image. Every container started from that image will have a valid license.

Build-time activation still requires Internet access. It is only needed during docker build, not when you run containers from the built image.

See Internet connectivity requirements for the licensing endpoint.

This is the recommended approach for production. It avoids repeating activation for each container.

Where to use it:

• Build using Dockerfile

• Build using prebuilt configuration

Option 2: Activate on container startup

Pass the license ticket as an environment variable:

• --env WPR_LICENSE_TICKET_ID=<license_ticket_id>

Example:

docker run -d \
  -p 80:8080 \
  --env WPR_LICENSE_TICKET_ID=<license_ticket_id> \
  local/wsc_app:6.9.0

This activation requires Internet access. It is not recommended for production. Use it for trials, especially when you run the public Docker Hub image.

During activation, the server must be able to reach the licensing endpoint. See Internet connectivity requirements for the exact URL and network requirements.

Verify license status

Use one of these methods:

• API-based health and remaining time:

  • Health check

• API-based reason when the license is not valid:

  • License status

• Log-based validation:

  • License verification

Common pitfalls

• Trial activation on startup needs outbound connectivity. It can fail on locked-down hosts.

• If you run multiple containers, build-time activation is simpler. You avoid activating per container.

• A license is tied to the product version. If you persist the license file in a mounted volume and then move to a newer image, the stored license no longer matches and the service stops serving requests. Re-activate after the upgrade. See Upgrade application version. Build-time activation is not affected, because a new image is activated during its own build.

Related pages

• Run the image from Docker Hub

• Internet connectivity requirements