Page Comparison

...

Then use the environment variable file to start the lipi

sudo docker run --rm --name lipi \
 --env-file=lipi-docker-env-file \
 -p 443:8080 \
  gcr.io/mazemap-public-docker/lipi:latest

To start the service in the background, add the --detach option:

sudo docker run --detach --rm --name lipi \
 --env-file=lipi-docker-env-file \
 -p 443:8080 \
  gcr.io/mazemap-public-docker/lipi:latest

...

By default this command prints everything logged since the container was started and then returns you to the command prompt. You may add the option --follow to see the log messages as they arrive. If the service has been running for a long time and you’re only interested in, say, messages from the last 5 minutes, use --since 5m. Putting it all together:

sudo docker logs --since 5m --follow lipi

Start Server with local config.json file

This is a special case, the normal case for production use is to start the service in the background, as described further up in this document.

sudo docker run --rm --name lipi \
    --env-file=lipi-docker-env-file \
    -v <your-config-path>:/app/resources/local_config.json \
    -p 443:8080 \
    gcr.io/mazemap-public-docker/lipi:latest

...

Changes to the LIPI configuration can be applied by deleting the container:

sudo docker rm -f lipi

And then starting again it in the same way as normal.

...