Build without internet connection

Use this workflow if the production host has no Internet access.

Build (or pull) the Docker image on a machine with Internet access. Then transfer it to the isolated host.

What you need

• Docker installed on the build machine and the production host.

• An image already built locally.

Save the image to a tar archive

docker save -o wsc_app.tar local/wsc_app

Transfer the tar file to the production host

Use scp (or rsync) over SSH:

scp wsc_app.tar [e-mail]:/path/on/remote

Load the image on the production host

docker load -i /path/on/remote/wsc_app.tar

Run the container on the production host

Use --env flags.

This avoids rebuilding images for environment-specific values.

Runtime values also override values baked into the image during docker build.

WPR_VIRTUAL_DIR=wscservice

docker run -d \
  -p 80:8080 \
  --env WPR_PROTOCOL=2 \
  --env WPR_WEB_PORT=80 \
  --env WPR_VIRTUAL_DIR=wscservice \
  local/wsc_app

WPR_VIRTUAL_DIR=/

docker run -d \
  -p 80:8080 \
  --env WPR_PROTOCOL=2 \
  --env WPR_WEB_PORT=80 \
  --env WPR_VIRTUAL_DIR=/ \
  local/wsc_app

The two common endpoints are:

WPR_VIRTUAL_DIR=wscservice

• Version: http(s)://<host>/wscservice/api?cmd=ver

• Status: http(s)://<host>/wscservice/api?cmd=status

WPR_VIRTUAL_DIR=/

• Version: http(s)://<host>/api?cmd=ver

• Status: http(s)://<host>/api?cmd=status

Use the checks from the README.

• Health and license time:

  • Health check

• Log-based license validation:

  • License verification