main / edge version -- I'm a bit worried we wrote some bad code, I did push a commit and pushed new images, but yeah LMK when you're around 👌
main / edge version -- I'm a bit worried we wrote some bad code, I did push a commit and pushed new images, but yeah LMK when you're around 👌
main / edge version -- I'm a bit worried we wrote some bad code, I did push a commit and pushed new images, but yeah LMK when you're around 👌
main / edge version -- I'm a bit worried we wrote some bad code, I did push a commit and pushed new images, but yeah LMK when you're around 👌
yarnd 0.15.1@81e22f8e on both my pods no worries. Maybe try updating to latest again? 🤔 
yarnd 0.15.1@81e22f8e on both my pods no worries. Maybe try updating to latest again? 🤔
yarnd 0.15.1@81e22f8e on both my pods no worries. Maybe try updating to latest again? 🤔
yarnd 0.15.1@81e22f8e on both my pods no worries. Maybe try updating to latest again? 🤔
prologic/yarnd:latest as well as prologic/yarnd:dev to match (normally I do this on a release, but this time...) -- Be aware I _may_ break your pod, so will need your help to debug this if you're around later...If/When you see this recommend taking a backup of your user config which you can do by hitting for example
https://twtxt.net/user/prologic/config.yaml when logged in and shove that somewhere. Worst case we just wipe your database and re-register. Can also temporarily set the admin account to some random new user, register that and forcibly do a password reset/change.But I'd rather we figure this out and fix the problem... I'm just not sure what it is yet 🤔
prologic/yarnd:latest as well as prologic/yarnd:dev to match (normally I do this on a release, but this time...) -- Be aware I _may_ break your pod, so will need your help to debug this if you're around later...If/When you see this recommend taking a backup of your user config which you can do by hitting for example
https://twtxt.net/user/prologic/config.yaml when logged in and shove that somewhere. Worst case we just wipe your database and re-register. Can also temporarily set the admin account to some random new user, register that and forcibly do a password reset/change.But I'd rather we figure this out and fix the problem... I'm just not sure what it is yet 🤔
prologic/yarnd:latest as well as prologic/yarnd:dev to match (normally I do this on a release, but this time...) -- Be aware I _may_ break your pod, so will need your help to debug this if you're around later...If/When you see this recommend taking a backup of your user config which you can do by hitting for example
https://twtxt.net/user/prologic/config.yaml when logged in and shove that somewhere. Worst case we just wipe your database and re-register. Can also temporarily set the admin account to some random new user, register that and forcibly do a password reset/change.But I'd rather we figure this out and fix the problem... I'm just not sure what it is yet 🤔
prologic/yarnd:latest as well as prologic/yarnd:dev to match (normally I do this on a release, but this time...) -- Be aware I _may_ break your pod, so will need your help to debug this if you're around later...If/When you see this recommend taking a backup of your user config which you can do by hitting for example
https://twtxt.net/user/prologic/config.yaml when logged in and shove that somewhere. Worst case we just wipe your database and re-register. Can also temporarily set the admin account to some random new user, register that and forcibly do a password reset/change.But I'd rather we figure this out and fix the problem... I'm just not sure what it is yet 🤔
Can you confirm the same as below for me on your end?
$ docker run -i -t --rm prologic/yarnd:latest yarnd --version
usermod: no changes
Configuring yarnd...Switching UID=1000 and GID=1000
yarnd edge@d35d2da6
Can you confirm the same as below for me on your end?
$ docker run -i -t --rm prologic/yarnd:latest yarnd --version
usermod: no changes
Configuring yarnd...Switching UID=1000 and GID=1000
yarnd edge@d35d2da6
Can you confirm the same as below for me on your end?
$ docker run -i -t --rm prologic/yarnd:latest yarnd --version
usermod: no changes
Configuring yarnd...Switching UID=1000 and GID=1000
yarnd edge@d35d2da6
Can you confirm the same as below for me on your end?
$ docker run -i -t --rm prologic/yarnd:latest yarnd --version
usermod: no changes
Configuring yarnd...Switching UID=1000 and GID=1000
yarnd edge@d35d2da6