»Tips and Troubleshooting
»Remove the Waypoint Server
The Waypoint Server creates several resources in Docker and Kubernetes that should be removed to either reinstall Waypoint or to completely remove it from a system.
»Waypoint Server in Docker
Ensure that you have the latest
hashicorp/waypoint Docker image.
$ docker pull hashicorp/waypoint:latest
waypoint install for Docker creates a container and a volume. These resources should be removed when Waypoint Server is no longer needed. These are some example
docker commands that should clean up after a Waypoint Server installation.
$ docker stop waypoint-server $ docker rm waypoint-server $ docker volume prune -f
»Waypoint Server in Kubernetes
waypoint install for Kubernetes creates a StatefulSet, Service and PersistentVolumeClaim. These resources should be removed when Waypoint Server is no longer needed. These are some example
kubectl commands that should clean up after a Waypoint Server installation.
$ kubectl delete statefulset waypoint-server $ kubectl delete pvc data-waypoint-server-0 $ kubectl delete svc waypoint
»Pack Builder No Such Image
pack builder exits during build with an error similar to:
» Building... Creating new buildpack-based image using builder: heroku/buildpacks:18 ... ! failed to create 'detector' container: Error response from daemon: No such image: pack.local/builder/6c647962686577687270:latest
You may need to remove the Docker volumes that are responsible for storing cached images for pack.
$ docker volume list ...
Locate the volumes named starting with
pack-cache- and remove them with
docker volume rm.
»Investigating deployed applications
Waypoint includes several commands to support debugging and monitoring while developing your application.
»Exec into the application container
After deploying your application, you can use
waypoint exec to run
commands in the context of the most recent deployment. Typically,
exec will be used for running database migrations and debugging. However, you
can use it for any purpose.
exec command to open a shell prompt.
$ waypoint exec /bin/bash
Since you are in the deployment directory, you will observe that Waypoint automatically executes against the currently deployed application.
From within the Docker container, validate that this is the actual application
by listing out the directory hosting the application's compiled files. For example, if you used the
pack builder this directory will be
$ cd / && ls
You should observe an output that contains the file structure for the current deployment.
List the processes that are running in the container.
$ ps aux
exit to leave the interactive Docker session.
»View Waypoint application logs
In the application's directory, run the
logs command to observe the running
logs for your deployment.
$ waypoint logs
You will observe output similar to the following. These logs are from the existing deployment.
2020-09-24T06:20:18.162Z 2MGFF4: 2020-09-24T06:20:18.163Z 2MGFF4: > email@example.com start /workspace 2020-09-24T06:20:18.163Z 2MGFF4: > node index.js 2020-09-24T06:20:18.163Z 2MGFF4: 2020-09-24T06:20:18.383Z 2MGFF4: Listening on 3000
Ctrl-C to exit the
»Access the Waypoint web UI
The Waypoint server includes a web-based user interface that you can use to view builds, deployments, and releases for projects and applications.
The web UI requires authentication. Run a single command to automatically open the browser and authenticate your session. This command will work if a graphical web browser is available on the machine where the command is being run.
$ waypoint ui -authenticate
NOTE: Waypoint currently uses self-signed certificates for TLS. Your web browser will require you to bypass a certificate warning to use the UI.
Review the application metadata and associated operations and logs in the browser.