Brev Debugging

This page has common hurdles or known issues that we’re addressing.

Reset Brev

If you’re noticing some workspaces to be missing or the Brev CLI is not working, use the Brev refresh command to try forcing a refresh to the ssh config and ensuring the daemon is started:

brev refresh

Issues with Custom Container / Docker Compose Builds

If you’re having issues with your container/docker compose builds failing, try the following to view errors in your logs:

brev shell <instance-name>

cd workspace

docker compose logs

If you’re having issues with your JupyterLab tunnel being unhealthy, double check to see if your container/Docker Compose is setting up a JupyterLab server.

Issues with permission denied while trying to connect to the Docker daemon socket

If you’re facing issues with permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock, try the following:

sudo chmod 666 /var/run/docker.sock

and then re-running your docker command(s).

See all the startup logs

Sometimes weird issues happen when configuring the machine, for example, the project folder is empty because ssh keys weren’t configured and the repo couldn’t be cloned.

You can view the full startup logs by running sudo cat /var/log/brev-workspace.log inside your workspace.