mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #286] Can't build for ARMV7 #155
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#155
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 @phischmi on GitHub (Dec 13, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/286
Hi all,
i'm trying to build the docker image for ARMV7, but whatever i try, the build always fail with the following error:
Is there anything i can do to make this work?
@mprasil commented on GitHub (Dec 13, 2018):
Are you actually building on armv7 device? There's
Dockerfile.armv7that's meant to be built on x86 device, but it cross-compiles to armv7.@phischmi commented on GitHub (Dec 13, 2018):
I'm building on an Odroid HC2 which is armv7
@mprasil commented on GitHub (Dec 13, 2018):
It seems like this might be an upstream issue, I'm not even sure if Vault actually can be built on armv7. Perhaps you can overcome this by using our image for the vault data? Just replace the Vault build stage with:
Then delete the rest up to the binary build image stage. (that starts with
FROM rust as build)@phischmi commented on GitHub (Dec 13, 2018):
That seems to work :) Thanks!
@mprasil commented on GitHub (Dec 13, 2018):
It's a bit of a workaround, but I guess there isn't much we can do here as the code is all upstream. I'm going to close this now, glad that it worked for you.
@thiscantbeserious commented on GitHub (Dec 28, 2018):
The issue above seems like one we've faced as well, a quiet ugly one at it.
node-sass is basically just a binding to LibSass - a native c++ sass compiler, node-sass (seriously) tries to look for Python and C++ binaries and/or tries to pull them to compile the underlying LibSass for your local environment to be able to comple Sass to CSS via the binding node-sass provides - resulting in one heck of a dependency mess that's hard to manage.
I'll create an issue in the official bitwarden repo for the webvault suggesting to switch to https://www.npmjs.com/package/sass which is a native JS SASS compiler that doesn't require any hacky dependencies out of its domain (JS).
The performance gains from node-sass are little compared to its actualy usecase from my experience (compiling about a hundred sass files for a frontend-framework that we've created).