Chris Van Pelt (CVP)
Chris Van Pelt (CVP)
Hey @bzamecnik you really shouldn't be running the instance with MySQL inside of the container. It's only for trial purposes and we should connect the instance to an external MySQL...
@bzamecnik exactly, the terraform in this repository can make that really straight forward.
Hey @lostork not sure how you got into that state. If you don't have any data in the instance, the simplest fix is to remove the persistent volume and start...
@carloalbertobarbano if you remove the volume, be sure to visit http://localhost:8080/logout or access the instance from an incognito window to ensure the initial account creation process is properly triggered.
@carloalbertobarbano these errors are being caused by the initial migration of the database failing. This is likely due to filesystem driver issues or other docker specific issues with the filesystem...
@leeyh20 I'm not sure this is related to a specific version of wandb or simply the amount of MySQL migrations that are required in later versions. Each release generally contains...
@carloalbertobarbano are you getting the "RELEASE LOCK" error, or the "entity already exists for user local" error? Can you share the output of `docker logs wandb-local`?
And the contents of `/var/log/mysql.log`?
This is helpful, MySQL is not allowing you to start it as root. Our system is designed to be started as an untrusted user as long as it's started with...
The new error is caused by a very slow filesystem. Can you try modifying the storage driver being used and starting with fresh volumes to see if you can find...