Vaultwarden 1.28.0 released #25
Comments
spantaleev
added a commit
that referenced
this issue
Mar 29, 2023
|
The permission problems are related to dani-garcia/vaultwarden#3386 Our Ansible role includes a workaround which adds the additional |
spantaleev
added a commit
to mother-of-all-self-hosting/ansible-role-vaultwarden
that referenced
this issue
Apr 3, 2023
oliverlorenz
pushed a commit
to oliverlorenz/ansible-role-matterbridge
that referenced
this issue
Jun 21, 2024
oliverlorenz
pushed a commit
to oliverlorenz/ansible-role-matterbridge
that referenced
this issue
Jun 21, 2024
oliverlorenz
pushed a commit
to oliverlorenz/ansible-role-matterbridge
that referenced
this issue
Jun 21, 2024
Fix incorrect tag Do not mount timezone files Rocky Linux 9 does not have an `/etc/timezone` file, which begs the question: why even do this? Upgrade (1.27.0 -> 1.28.0) Fixes mother-of-all-self-hosting/mash-playbook#25 Switch from docker.io to ghcr.io Upgrade (1.28.0 -> 1.28.1) and drop NET_BIND_SERVICE workaround Related to: - mother-of-all-self-hosting/mash-playbook#25 - dani-garcia/vaultwarden#3387 - dani-garcia/vaultwarden#3403 Upgrade (1.28.1 -> 1.29.0) and remove dedicated WebSocket port As per dani-garcia/vaultwarden#3404, we no longer need a dedicated websocket port. Upgrade (1.29.0 -> 1.29.1) Add missing Project source code URL annotation Upgrade (1.29.1 -> 1.29.2) Split vaultwarden_container_additional_networks into vaultwarden_container_additional_networks_auto and vaultwarden_container_additional_networks_custom Add a variable dedicated to the --hostname parameter of the service unit file, default value is vaultwarden_hostname Simplify labels Upgrade (1.29.2 -> 1.30.0) Upgrade (1.30.0 -> 1.30.1) Stop the container gracefully, instead of outright killing it Add vaultwarden_systemd_wanted_systemd_services_list and split required services list into multiple vars Upgrade (1.30.1 -> 1.30.2) Upgrade (1.30.2 -> 1.30.3) copied to own repository
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please update playbook to use a new 1.28.0 release of Vaultwarden server.
Also simple addition of var
vaultwarden_version: 1.28.0doesn't work.mash-vaultwarden.serviceexits with an error, in the log:It seems docker
--cap-drop=ALLoption is the root of this issue. But on 1.27.0 it works well.After removing
--cap-drop=ALLline from service template the container run successfully. This is a workaround, not a fix though.The text was updated successfully, but these errors were encountered: