raspiblitz: Tor repo doesn't support architecture 'armhf' (32bit ARM) - need to compile from source?
This is a possible issue for all newly set up Tor nodes:
$ sudo apt update
Hit:5 https://deb.torproject.org/torproject.org buster InRelease
N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'https://deb.torproject.org/torproject.org buster InRelease' doesn't support architecture 'armhf'
Reported in RaspiBolt: https://github.com/Stadicus/RaspiBolt/issues/656
If this remains to be an issue there are two obvious solutions:
- switch to a 64bit base image (https://github.com/rootzoll/raspiblitz/issues/1199 - aimed for v1.7)
- compile Tor from source (can help to get around some issues with some ISP censorship since can be downloaded from github)
Methods to compile Tor from source:
- https://t.me/RaspiBlitzFAQ/168
- https://tor.stackexchange.com/questions/75/how-can-i-install-tor-from-the-source-code-in-the-git-repository
sudo apt-get install -y git build-essential automake libevent-dev libssl-dev zlib1g-dev # git clone https://git.torproject.org/tor.git git clone https://github.com/torproject/tor cd tor ./autogen.sh ./configure --disable-asciidoc make make install
-
https://2019.www.torproject.org/docs/debian#source
# https://2019.www.torproject.org/docs/debian#source echo "# running on armv6l - need to compile Tor from source" apt install -y build-essential fakeroot devscripts apt build-dep -y tor deb.torproject.org-keyring mkdir ~/debian-packages; cd ~/debian-packages apt source tor cd tor-* debuild -rfakeroot -uc -us cd .. dpkg -i tor_*.deb # setup Tor in the backgound # TODO - test if remains in the background after the Tor service is started tor &
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (6 by maintainers)
Adding
[arch=arm64]
seems to help:Then I get no warnings.
On a fresh 1.7.1 image I did:
raspiblitz is runing fine so far.
Compiled Tor with this simple script (from https://2019.www.torproject.org/docs/debian#source):
on a RPi4 4GB upgraded Tor successfully (the node is up and running):
Question is if we should take up with the 36 mins build time or maybe should ship the tor_*.debs on the SDcard (compile in the build_sdcard.sh) even if it is not active by default (before v1.7)?
I merged the PR 1769 and for the next v1.6.2 release sd card image I will run once manually the
update
so that the self buil packages will already we on the sd card. Putting on final testing for RC1.@openoms is there a specific feature/setting that we want/need from tor 0.4.X ? Or could we live with 0.3.5?