Some times we need reset password in order to login

[wztdream]

Hi, This not happens each time when I tried to login wandb/local. Some times I login normally, but sometimes the login page says: "invalid password", so I have to reset the pass word in order to log in. I am pretty sure I used the correct password each time.

[vanpelt]

@wztdream how are you running the container? If you're running it in kubernetes you must only have a single replica. Running it with multiple replicas will cause this behavior.

[wztdream]

@vanpelt I just run wandb local in terminal (I use ubuntu20.04 by the way), then there will be a link(localhostxxxx) shows up, then I click the link and open an login page in firefox, then I login and sometimes the issue comes up. Is there something wrong of these steps?

BTW, before I run wandb local, I need to run sudo chmod 666 /var/run/docker.sock, or else there will be permition error, maybe the issue relates with this command?

[kong13661]

I have the same problem. I find the file /vol/env/users.htpasswd become empty. So I have to use the command /usr/local/bin/local password to reset the password. I use the command docker run -e LOCAL_RESTORE=true --rm -d -v wandb:/vol -p 40200:8080 --name wandb-local wandb/local to create the docker container.

[ramit-wandb]

Hi @kong13661 @wztdream,

This is a known issue which we plan to resolve in the future - this does happen even if not running through kubernetes. I'll keep you updated on the status of its progress.

Thanks, Ramit

[ramit-wandb]

Hi! Just wanted to provide an update here - our engineering team looked into this issue and has pushed a fix which should be sent out with our next version of W&B Local. Please let us know if it does not operate as expected!

I'm closing this issue for now but feel free to reopen this thread if this issue is still a problem after the next release.

[dcfidalgo]

Hi, I am experiencing the same issue with version wandb/local 0.27.0. Every time I log out of our local instance, I have to reset the password to log in again. We use the following command to run the container: docker run --rm -d -v /root/wandb_vol:/vol -p 80:8080 --name wandb-local wandb/local Any ideas on what the culprit could be?