mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #2601] Upgrade to newest git commit fails using docker-compose #1320
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#1320
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 @bokkabonga on GitHub (Jul 7, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2601
Subject of the issue
When trying to upgrade from 1.24 to the newest version using "docker-compose build" it fails to build.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SENDS_ALLOWED, HIBP_API_KEY, USER_ATTACHMENT_LIMIT, ORG_ATTACHMENT_LIMIT, TRASH_AUTO_DELETE_DAYS, SIGNUPS_ALLOWED, SIGNUPS_VERIFY, SIGNUPS_VERIFY_RESEND_TIME, SIGNUPS_VERIFY_RESEND_LIMIT, SIGNUPS_DOMAINS_WHITELIST, INVITATIONS_ALLOWED, ADMIN_TOKEN, INVITATION_ORG_NAME, DISABLE_2FA_REMEMBER, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY, SMTP_HOST, SMTP_SSL, SMTP_PORT, SMTP_FROM, EMAIL_TOKEN_SIZE, EMAIL_EXPIRATION_TIME
Install method: docker-compose
MySQL/MariaDB or PostgreSQL version: MariaDB
OS: Oracle 7.9
Steps to reproduce
Expected behaviour
Building the container passes without problem
Actual behaviour
Building fails with Error (see below)
Troubleshooting data
" => ERROR [build 12/13] RUN cargo build --features mysql --release 37.8s
failed to solve: process "/bin/sh -c cargo build --features ${DB} --release" did not complete successfully: exit code: 101"
@bokkabonga commented on GitHub (Jul 7, 2022):
The same procedure works fine on Oracle 8.5. So i suspect it has something to do with some dependency maybe?
@BlackDex commented on GitHub (Jul 7, 2022):
Well, dependencies would be strange as those should all be inside the container. A container build can't be different on two separate hosts with the exact same git checksum.
I see a
sigkill killthere, that does look like depleted resources like memory for example.@bokkabonga commented on GitHub (Jul 7, 2022):
Yeah you are completely right. The server only had 2 GB of RAM. It seems thats not enough anymore. I assigned 4 GB to the server now and it works again like a charm :)