Chris Van Pelt (CVP)

You can find details about what our process is doing by looking at the `wandb/debug-internal.log` process relative to your script. We would need to see that to understand what's making...

MySQL is unable to start. You can find logs for MySQL at /var/log/mysql.log which should tell us why it's not able to start.

@GFiz we just released a new version of the server that should address this problem. Can you try upgrading and report back?

@llan-ml it looks like WSL2 doesn't play nicely with our internal mysql. You can run mysql directly on your machine or in a separate container. Instructions here: https://docs.wandb.ai/guides/self-hosted/setup/on-premise-baremetal#mysql-database

@GFiz you'll need to run mysql outside of the container and specify it's connection string with the MYSQL environment variable.

@GFiz most of our customers run this in a cloud that provides a managed MySQL instance. We have terraform and instructions for deploying into clouds here: https://docs.wandb.ai/guides/self-hosted If you can't...

Hey @erhlloyd have you tried using a smaller batch size? The default in the example uses 100, i.e. `CALL batch_delete(100, 1);` reducing this to 10 or even lower should reduce...

How long of a delay are you seeing? It generally shouldn't take longer than 30 seconds for any logged images to appear.

Hey @niclaswue can share how you're getting "hostname" to resolve in your network? The most useful log here would be `/var/log/gorilla.log` as it looks like our service is unable to...

You can specify a userid for the docker container to launch as. As long as the container is started with the root group (0) and that group has write permissions...