[GH-ISSUE #269] docker arm builds are failing,can't download node-sass #141

New issue

Closed

opened 2026-03-03 01:25:44 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:25:44 +03:00

Owner

Originally created by @nutspie-bot on GitHub (Nov 22, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/269

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). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/269 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 ```

kerem closed this issue

2026-03-03 01:25:44 +03:00

kerem commented

2026-03-03 01:25:45 +03:00

Author

Owner

@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

kerem commented

2026-03-03 01:25:45 +03:00

Author

Owner

@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?

kerem referenced this issue

2026-03-03 02:20:07 +03:00

[PR #141] [MERGED] Add PUT alias for profile update #2631