Chris Van Pelt (CVP)

We understand your fear and are adding more tests to prevent upgrade failures like this in the future. 0.21.0 had a regression which caused volumes created previously to fail upgrading....

Sorry about the 2 lines not working, we'll investigate and reproduce the workspace error and provide lines that work. You should never lose data, that's unacceptable.

@Jeffrey28 I just verified lines that work when upgrading from a volume that was first mounted on version 0.21.0, to a server running 0.22.0: ``` docker exec -it wandb-local sudo...

It looks like the wandb/local server isn't running. Are you able to access the instance at http://localhost:8080 from your browser? If you can share the output of the container logs...

Sorry, I meant `docker logs wandb-local` that should display the appropriate errors. I also noticed you're trying to access the service on http://localhost:8081. If you're not going to access the...

Hey @ethanabrooks `wandb init` is meant for initializing a directory and requires a terminal that has user input. What you likely want to be doing is calling `wandb.init(project="test-project")` inside of...

Also, can you share a little more information about why you're using docker-compose and running a local server instead of using our cloud service? Generally users deploy the local service...

What do you see when you goto `http://localhost:8080`? The 502 error, means the wandb service isn't configured properly o failed to boot for some reason. You likely don't want to...

Sorry, I meant going to http://localhost:8080 in your web browser and seeing if there are any errors displayed on our application page.

Hey @ethanabrooks, you'll likely need to stop the docker-compose stack entirely and then run up. I.E. `docker-compose stop` instead of just `docker-compose down`. The other error you're seeing is being...