Closed shofutex closed 5 months ago
Hi there,
I attempted to reproduce your issue and was unable to do so, so this may be an environmental or dependency issue.
We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).
You can include a link to this issue in the message content.
Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).
The issue here will be closed.
Thanks!
I will check further, but it is related to: https://github.com/bitwarden/server/issues/3755
This is the error:
bitwarden_1 | Adding user bitwarden' to group
users' ...
db_1 | 2024-02-10 23:36:14 0 [Note] InnoDB: Buffer pool(s) load completed at 240210 23:36:14
db_1 | 2024-02-10 23:36:14 0 [Note] mariadbd: ready for connections.
db_1 | Version: '10.11.6-MariaDB-1:10.11.6+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
bitwarden_1 | You must install or update .NET to run this application.
bitwarden_1 |
bitwarden_1 | App: /usr/local/bin/hbs
bitwarden_1 | Architecture: x64
bitwarden_1 | Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
bitwarden_1 | .NET location: /usr/share/dotnet
bitwarden_1 |
bitwarden_1 | The following frameworks were found:
bitwarden_1 | 8.0.1 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
bitwarden_1 |
bitwarden_1 | Learn more:
bitwarden_1 | https://aka.ms/dotnet/app-launch-failed
bitwarden_1 |
bitwarden_1 | To install missing framework, download:
bitwarden_1 | https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=linux-x64&os=debian.12
I tried to pull 2024.2.0-beta and bitwarden doesn't start. There are no updates to the logs since starting this container and I get an empty reply from server trying to connect.
Switching back to 2024.1.2 is the only resolution.
Without logs updating, is there something I can do to get more insight into why 2024.2.0 is crashing?