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_appTransfer the tar file to the production host
Use scp (or rsync) over SSH:
scp wsc_app.tar REMOTE_USER@xx.xx.xx.xx:/path/on/remoteLoad the image on the production host
docker load -i /path/on/remote/wsc_app.tarRun the container on the production host
Use --env flags.\nThis avoids rebuilding images for environment-specific values.
Example (HTTP):
Verify
Status endpoint:
http://<host>/<virtual_dir>/api?cmd=statusVersion endpoint:
http://<host>/<virtual_dir>/api?cmd=ver
If you use the defaults above:
http://localhost/wscservice/api?cmd=statushttp://localhost/wscservice/api?cmd=ver
Last updated
Was this helpful?

