NAS encounters the issue about network slow, that causes the migrate task failure, however, network is normal.

[LiuWhale]

System

Linux 4.4.302+ #69057 SMP Fri Jan 12 17:02:59 CST 2024 x86_64 GNU/Linux synology_apollolake_918+

Docker version

• Docker version 20.10.23, build 876964a

Python version

• 3.11.5

wandb version

• 0.18.5

docker run --rm -d -e LICENSE=mylicense -p 6009:8080  --name wandb-local wandb/local

[luisbergua]

Hey @LiuWhale, thanks for writing in! Would you mind sharing which version are you running currently? I would recommend ensuring that you're running the latest version (see here, 0.61.0). If this still fails, could you please try running the steps here and seeing if that causes any issues? By following those you shouldn't face any issue, and can apply the license in the UI so curious to know if this would work for you.

[LiuWhale]

Hey @LiuWhale, thanks for writing in! Would you mind sharing which version are you running currently? I would recommend ensuring that you're running the latest version (see here, 0.61.0). If this still fails, could you please try running the steps here and seeing if that causes any issues? By following those you shouldn't face any issue, and can apply the license in the UI so curious to know if this would work for you.

I tried with wandb command, but an issue is shown as below, that's why run server manually.

[LiuWhale]

When I try with wandb docker-run command, new issue is showed up.

[luisbergua]

Thanks for sharing this @LiuWhale! Would you mind sharing what version are you using? Also, I see the image was created 2 weeks ago, so I would recommend removing it and the container and trying again in a fresh environment with the wandb server start command. It might be that there's something wrong with your current image

[LiuWhale]

The wandb image is latest version, same as docker hub’s one. The digest code is same too.

Thanks for sharing this @LiuWhale! Would you mind sharing what version are you using? Also, I see the image was created 2 weeks ago, so I would recommend removing it and the container and trying again in a fresh environment with the wandb server start command. It might be that there's something wrong with your current image

[LiuWhale]

I’m considering about the influence of system, the image is running well on Ubuntu, after all.

[luisbergua]

Hi @LiuWhale, thanks for confirming this! Yes that could be affecting, I would recommend trying in a fresh environment from scratch (and maybe a different machine). Please let me know if you still see the issue after doing that!

[luisbergua]

Hey Liu, closing this for now but feel free to re-open if you need any other assistance