mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #149] Latest docker image has still version 1 #73
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Aug 22, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/149
I use image from https://hub.docker.com/r/mprasil/bitwarden/tags/ with lastest tag.
Web interface is old, not the newest 2.2.0
@mprasil commented on GitHub (Aug 22, 2018):
You must be running some older image, I've literary just pulled and launched the container and it's bundled with 2.1.1 version of Vault. (the latest released)
@mprasil commented on GitHub (Aug 22, 2018):
Just to add, you can see latest buid log here. It clearly builds 2.1.1 Vault. Try to run
docker pull mprasil/bitwardenbefore running your container.@fbartels commented on GitHub (Aug 22, 2018):
Just replying since this seems like a small number confusion:
@dani-garcia commented on GitHub (Aug 22, 2018):
Version 2.2 is still not released according to
https://github.com/bitwarden/web/releases
We’ll wait until an official release before bumping the included version.
@ghost commented on GitHub (Aug 22, 2018):
Sorry all for my mistake. I use Portainer to manage my docker containers and it did not pull the newest image when I create new container.
So I use the newest one 2.1.1 but have problem with web interface response time, it is slower than version 1.
Do someone has the same problem?
@mprasil commented on GitHub (Aug 22, 2018):
What do you mean by slower @Haxy89 ? Like generally navigating ciphers, searching and so on, or something that hits server like saving changes, moving between folders and the like?
I can't really say I've noticed any slowness, but it's generally javascript heavy application and I can see how it can be slower on less powerful PCs.
@ghost commented on GitHub (Aug 22, 2018):
@mprasil
Displaying login page tooks 30seconds, login to main view took 10-20seconds. Before update to 2.1.1 everythings worked faster
@mprasil commented on GitHub (Aug 22, 2018):
That sounds like some javascript related issue. Did you try to check in the developer tools in browser on the network tab how the requests get through? The login screen loads for me in about a second, so this indeed sound slow but not really related to server changes.
The initial load after login can be affected by server changes (due to slow sync) but there were no major changes server-side between V1 and V2 so it sounds unlikely. How many passwords do you have stored?