starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

docker arm builds are failing,can't download node-sass #139

New Issue
Closed
opened 2026-02-04 17:51:19 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 17:51:19 +03:00
Owner
Copy Link

Originally created by @nutspie-bot on GitHub (Nov 22, 2018).

The node-sass module unsupported ARM.

> node-sass@4.9.3 install /web-build/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.3/linux-arm-57_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.3/linux-arm-57_binding.node": 

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g. 

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080
Originally created by @nutspie-bot on GitHub (Nov 22, 2018). The node-sass module unsupported ARM. ``` > node-sass@4.9.3 install /web-build/node_modules/node-sass > node scripts/install.js Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.3/linux-arm-57_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.3/linux-arm-57_binding.node": HTTP error 404 Not Found Hint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g. export HTTP_PROXY=http://example.com:1234 or configure npm proxy via npm config set proxy http://example.com:8080 ```
OVERLORD commented 2026-02-04 17:51:50 +03:00
Author
Owner
Copy Link

@TBK commented on GitHub (Nov 22, 2018):

Discussion on the matter https://github.com/sass/node-sass/pull/2253

@TBK commented on GitHub (Nov 22, 2018): Discussion on the matter https://github.com/sass/node-sass/pull/2253
OVERLORD commented 2026-02-04 17:51:56 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Nov 22, 2018):

I don't think we can do anything on our side. Maybe you can report the issue in the upstream? As for our ARM build, we're actually building the Vault on x86 platform and we also cross-compile the server binary on x86, (this is so we can have automated build on docker hub) so our builds shouldn't be affected by this. Maybe you can use the raspberry image from docker hub or build your own on x86?

@mprasil commented on GitHub (Nov 22, 2018): I don't think we can do anything on our side. Maybe you can report the issue in the [upstream](https://github.com/bitwarden/web)? As for our [ARM build](https://github.com/dani-garcia/bitwarden_rs/blob/master/Dockerfile.armv7), we're actually building the Vault on x86 platform and we also cross-compile the server binary on x86, (this is so we can have automated build on docker hub) so our builds shouldn't be affected by this. Maybe you can use the raspberry image from docker hub or build your own on x86?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear 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
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#139
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?