Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitwarden Unified - api (terminated by SIGABRT (core dumped); not expected) #2493

Closed
1 task done
Kizaing opened this issue Dec 12, 2022 · 2 comments
Closed
1 task done
Assignees
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment

Comments

@Kizaing
Copy link

Kizaing commented Dec 12, 2022

Steps To Reproduce

  1. Use docker compose to create the bitwarden unified and maria db containers
  2. Check the logs to see it immediately failed due to (terminated by SIGABRT (core dumped); not expected) error

Expected Result

The expected result was for the unified bitwarden container services to start

Actual Result

All unified container services immediately fail (icons, notifications, admin, api, identiy) all fail with the error (terminated by SIGABRT (core dumped); not expected).

Looking inside the container to check the logs, each service has specifically failed with this error:

Unhandled exception. System.InvalidOperationException: Failed to convert configuration value at 'GlobalSettings:Installation:Id' to type 'System.Guid'.

Screenshots or Videos

No response

Additional Context

No response

Githash Version

N/A, the API service fails to start

Environment Details

  • Operating System: Ubuntu Server 22.04 via Hyper-V in Windows 11
  • Environment: Docker
  • Hardware: Core i7 1270P

Database Image

mariadb:10

Issue-Link

#2480

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@Kizaing Kizaing added bug bw-unified-deploy An Issue related to Bitwarden unified deployment labels Dec 12, 2022
@vgrassia
Copy link
Member

Hi @Kizaing, along with the docker-compose.yml file, you'll need to provide a settings.env file which has required settings for the container to come up correctly.

@vgrassia vgrassia self-assigned this Dec 12, 2022
@Kizaing
Copy link
Author

Kizaing commented Dec 13, 2022

Apologies, I did have the settings.env file but I missed putting in a variable, marking issue as closed. Thank you!

@Kizaing Kizaing closed this as completed Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment
Projects
None yet
Development

No branches or pull requests

2 participants