samourai-dojo issueshttps://code.samourai.io/dojo/samourai-dojo/-/issues2023-12-15T14:21:36Zhttps://code.samourai.io/dojo/samourai-dojo/-/issues/162dojo.sh complains every time with "docker: 'compose' is not a docker command"2023-12-15T14:21:36Zjaimedojo.sh complains every time with "docker: 'compose' is not a docker command"The solution would be to just add 2& to > /dev/null so this error message is not shown. Like this:
Line 9:
` if docker compose version 2&> /dev/null ; then`The solution would be to just add 2& to > /dev/null so this error message is not shown. Like this:
Line 9:
` if docker compose version 2&> /dev/null ; then`https://code.samourai.io/dojo/samourai-dojo/-/issues/161Whirlpool port not exposed via nginx2023-07-24T09:05:24ZMr HashWhirlpool port not exposed via nginxWasn't able to access whirlpool via onion address, solved it by adding port 8898 to the nginx exposed ports here https://code.samourai.io/dojo/samourai-dojo/-/blob/develop/docker/my-dojo/docker-compose.yaml#L73-75.Wasn't able to access whirlpool via onion address, solved it by adding port 8898 to the nginx exposed ports here https://code.samourai.io/dojo/samourai-dojo/-/blob/develop/docker/my-dojo/docker-compose.yaml#L73-75.https://code.samourai.io/dojo/samourai-dojo/-/issues/160Lack of .cookie auth for Bitcoin Core2023-01-04T21:57:45ZDanielPXLack of .cookie auth for Bitcoin CoreIn DIY set up of Dojo, only way to connect BTC core is by using plain text credentials. While this can be mitigated by restricting access to config file, it would be nice and security friendly feature to use .cookie file for authenticati...In DIY set up of Dojo, only way to connect BTC core is by using plain text credentials. While this can be mitigated by restricting access to config file, it would be nice and security friendly feature to use .cookie file for authentication / maybe not that complicated to implementhttps://code.samourai.io/dojo/samourai-dojo/-/issues/159docs: Running remove command ends in error2022-09-15T14:12:57ZSarekdocs: Running remove command ends in errorIn first-time install docs on Line 70, it says to run the following command to remove any pre-existing installation:
`sudo apt-get remove docker docker-engine docker.io containerd runc`
https://code.samourai.io/dojo/samourai-dojo/-/blo...In first-time install docs on Line 70, it says to run the following command to remove any pre-existing installation:
`sudo apt-get remove docker docker-engine docker.io containerd runc`
https://code.samourai.io/dojo/samourai-dojo/-/blob/develop/doc/DOCKER_ubuntu_setup.md#L70
However, in Ubuntu 22.04 LTS (not sure if it's unique to that or not), the command returns an error:
```bash
~$ sudo apt remove docker docker-engine docker.io containerd runc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package docker-engine
```
It doesn't matter what position the `docker-engine` argument is in. If you remove that one, the command completes as expected:
```bash
~$ sudo apt remove docker docker.io containerd runc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'containerd' is not installed, so not removed
Package 'runc' is not installed, so not removed
Package 'docker' is not installed, so not removed
Package 'docker.io' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
```
So for the sake of First Time Installation and new users, the command should probably be modified so as to not return an error without completing the desired outcome. Either by splitting the command up so the functional part completes and then the one that could error out will fail on its own, or maybe the `docker-engine` isn't the right package name? I don't know.https://code.samourai.io/dojo/samourai-dojo/-/issues/158Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead2022-09-15T14:13:22ZSarekWarning: apt-key is deprecated. Manage keyring files in trusted.gpg.d insteadWhen I run the installation command below:
```
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - && sudo apt-key fingerprint 0EBFCD88
```
Which comes from Lines 76 and 77:
https://code.samourai.io/dojo/samou...When I run the installation command below:
```
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - && sudo apt-key fingerprint 0EBFCD88
```
Which comes from Lines 76 and 77:
https://code.samourai.io/dojo/samourai-dojo/-/blob/develop/doc/DOCKER_ubuntu_setup.md#L76
It completes but returns a warning:
`Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).`
This is in a fresh install of Ubuntu 22.04 LTS. I recommend adopting the recommended approach, though I don't know how to go about it myself.https://code.samourai.io/dojo/samourai-dojo/-/issues/157Unable to Establish a Tor Connection2022-09-13T17:02:34Zbitcoiner anonUnable to Establish a Tor ConnectionHello,
I've been trying to install Dojo on a bare metal Ubuntu 22.04 installation
and the docker container doesn't seem to be able to connect to any tor
relay node.
The error that I was getting was similar to this issue:
https://code....Hello,
I've been trying to install Dojo on a bare metal Ubuntu 22.04 installation
and the docker container doesn't seem to be able to connect to any tor
relay node.
The error that I was getting was similar to this issue:
https://code.samourai.io/dojo/samourai-dojo/-/issues/82
But this Ubuntu instance is not running connman. I've also updated the Dojo
installation to the latest version a while ago.
`[...]
tor | Jul 20 14:52:06.000 [warn] 39 connections have failed:
tor | Jul 20 14:52:06.000 [warn] 39 connections died in state connect()ing with SSL state (No SSL object)
tor | Jul 20 14:52:14.000 [warn] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out; TIMEOUT; count 41; recommendation warn; host 320DB7BEA72C058BA2EEF098BF1AEFBA29371BE0 at 185.72.244.24:443)
[...]`
Regards,
Bitcoinerhttps://code.samourai.io/dojo/samourai-dojo/-/issues/156Indexer error wont start doocker container2022-07-17T19:30:00Zbob downIndexer error wont start doocker containerHi get this error in indexer container,what would cause it? all other containers are up.
```
indexer | Error: Failed to parse argument '--network': Unknown network (type mainnet).
indexer |
indexer | Hint: the value must be...Hi get this error in indexer container,what would cause it? all other containers are up.
```
indexer | Error: Failed to parse argument '--network': Unknown network (type mainnet).
indexer |
indexer | Hint: the value must be either 'bitcoin', 'testnet' or 'regtest'.
```https://code.samourai.io/dojo/samourai-dojo/-/issues/155Bitcoind RPC API Unreachable2022-03-08T21:17:57ZSilarousBitcoind RPC API UnreachableI am currently following the instructions [here](https://code.samourai.io/dojo/samourai-dojo/-/blob/develop/doc/DOCKER_advanced_setups.md#external_bitcoind) to setup the Dojo to connect to my Bitcoin node that is already running on the s...I am currently following the instructions [here](https://code.samourai.io/dojo/samourai-dojo/-/blob/develop/doc/DOCKER_advanced_setups.md#external_bitcoind) to setup the Dojo to connect to my Bitcoin node that is already running on the same machine. I have rpcauth=raspibolt:generatedpasswordhere in my bitcoin.conf file and I edited the fields in the docker-bitcoind.conf.tpl file, BITCOIND_RPC_USER=raspibolt, and BITCOIN_RPC_PASSWORD=passwordinplaintext.
I can not get the Dojo to connect to the Bitcoind RPC. All ports/ips are set in config files as necessary. I have also tried connecting via a rpcuser and rpcpassword in plaintext in both the bitcoin.conf and docker-bitcoind.conf files while disabling the rpcauth= setting but that was also unsuccessful. I completely disabled the ufw firewall, that was also unsuccessful. I have BTC-RPC_EXPLORER, Mempool.space, Specter and Fulcrum instances that are connecting to the same node just fine.
Is there a special way the rpcauth information needs to be entered in the docker-bitcoind.conf file? I've spent hours trying to get this to work. I'm sure I am missing something some where.
![image](/uploads/dc1899627cf10691a2f7246844b5ca42/image.png)
![image](/uploads/eee931ec795ac9ae1384703c1264a8bd/image.png)
![image](/uploads/8f586feb01c13961d29aab26dda40b9e/image.png)https://code.samourai.io/dojo/samourai-dojo/-/issues/154Error using ElectrumX or Fulcrum as indexer2022-02-04T21:19:26Zdecentralized.bError using ElectrumX or Fulcrum as indexerI configurated electrumX and Fulcrum to be used as an indexer, following the instructions described in Advanced Setup from this URL: https://docs.samourai.io/dojo/advanced-usage.
But when I upgrade the Dojo instance in my machine, I cou...I configurated electrumX and Fulcrum to be used as an indexer, following the instructions described in Advanced Setup from this URL: https://docs.samourai.io/dojo/advanced-usage.
But when I upgrade the Dojo instance in my machine, I could see the error shown below. The connection is ok, but something crashed when trying to gain or parse info from Sources.getChainTipHeight()
In DMT, the indexer status is yellow and does not show last block information.
![image](/uploads/2b4a9d0f41a03947a5c36654f1d0d253/image.png)
The setup is Dojo Vanilla:
Ubuntu 20.04.3 LTS, Dojo 1.13.0, electrumX 1.16.0 from https://github.com/spesmilo/electrumx.git
and Fulcrum from https://github.com/cculianu/Fulcrum
Error is the same with electrumX or Fulcrum
**Error trace:**
nodejs | 2022-01-29T13:49:41Z ERROR Importer : Sources.getChainTipHeight() : Error while retrieving the chaintip
nodejs | Error: Indexer JSON-RPC: host=192.168.0.30 port=50001: Error Parsing JSON: {"code":-32602,"message":"1 argument passed to method blockchain.headers.subscribe taking at most 0"}, data: {"jsonrpc": "2.0", "error": {"code": -32602, "message": "1 argument passed to method blockchain.headers.subscribe taking at most 0"}, "id": 0}
nodejs |
nodejs | at Socket.<anonymous> (file:///home/node/app/lib/indexer-rpc/rpc-client.js:204:33)
nodejs | at Socket.emit (events.js:400:28)
nodejs | at addChunk (internal/streams/readable.js:293:12)
nodejs | at readableAddChunk (internal/streams/readable.js:263:11)
nodejs | at Socket.Readable.push (internal/streams/readable.js:206:10)
nodejs | at TCP.onStreamRead (internal/stream_base_commons.js:188:23)https://code.samourai.io/dojo/samourai-dojo/-/issues/153Installation on synology: nodejs permissions2022-01-04T21:01:38ZBTC DavidInstallation on synology: nodejs permissionsHi,
I have installed Dojo on my Synology NAS.
When I try to connect to DMT through tor-browser, I get an error.
Looking into the logs, I see that node is not working properly.
Something to do with permission within the container.
If i...Hi,
I have installed Dojo on my Synology NAS.
When I try to connect to DMT through tor-browser, I get an error.
Looking into the logs, I see that node is not working properly.
Something to do with permission within the container.
If i log into the container, I would expect 'node' user to be owner of the relevant folders, but it is not...
The user 'node' does not have privileges to access both:
/home/node/app/pushtx/index-orchestrator.js and /home/node/app/pushtx/index-orchestrator.js
Can you help me change the appropriate config-files and then reinstall the image, so it will work persistantly?
Ive been trying to look for the solution myself for quite some time now, but this is a bit over my head.
Thanks
Here are the logs from node:
```bash
Attaching to nodejs
nodejs | code: 'EACCES',
nodejs | path: '/home/node/app/pushtx/index.js'
nodejs | }
nodejs | error: Forever detected script exited with code: 1
nodejs | (node:82) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
nodejs | (Use `node --trace-warnings ...` to show where the warning was created)
nodejs | internal/fs/utils.js:332
nodejs | throw err;
nodejs | ^
nodejs |
nodejs | Error: EACCES: permission denied, open '/home/node/app/pushtx/index-orchestrator.js'
nodejs | at Object.openSync (fs.js:497:3)
nodejs | at Object.readFileSync (fs.js:393:35)
nodejs | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1112:18)
nodejs | at Module.load (internal/modules/cjs/loader.js:950:32)
nodejs | at Function.Module._load (internal/modules/cjs/loader.js:790:12)
nodejs | at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
nodejs | at internal/main/run_main_module.js:17:47 {
nodejs | errno: -13,
nodejs | syscall: 'open',
nodejs | code: 'EACCES',
nodejs | path: '/home/node/app/pushtx/index-orchestrator.js'
nodejs | }
nodejs | error: Forever detected script exited with code: 1
nodejs | warn: --minUptime not set. Defaulting to: 1000ms
nodejs | warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
nodejs | info: Forever processing file: index.js
nodejs | (node:89) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
nodejs | (Use `node --trace-warnings ...` to show where the warning was created)
nodejs | (node:89) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
nodejs | (node:122) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
nodejs | (Use `node --trace-warnings ...` to show where the warning was created)
nodejs | internal/fs/utils.js:332
nodejs | throw err;
nodejs | ^
nodejs |
nodejs | Error: EACCES: permission denied, open '/home/node/app/tracker/index.js'
nodejs | at Object.openSync (fs.js:497:3)
nodejs | at Object.readFileSync (fs.js:393:35)
nodejs | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1112:18)
nodejs | at Module.load (internal/modules/cjs/loader.js:950:32)
nodejs | at Function.Module._load (internal/modules/cjs/loader.js:790:12)
nodejs | at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
nodejs | at internal/main/run_main_module.js:17:47 {
nodejs | errno: -13,
nodejs | syscall: 'open',
nodejs | code: 'EACCES',
nodejs | path: '/home/node/app/tracker/index.js'
nodejs | }
nodejs | error: Forever detected script exited with code: 1
```
And these are the logs of nginx:
```bash
Attaching to nginx
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
nginx | Operation timed out
```https://code.samourai.io/dojo/samourai-dojo/-/issues/152Dojo tor/obfs4proxy Failed To Build2022-02-04T21:23:32ZHardlyCodeManDojo tor/obfs4proxy Failed To BuildRaspi 4 4gb
Following instructions - https://docs.samourai.io/dojo/first-install with advanced config to allow for local bitcoind instance.
Ran `./dojo.sh install` as required. Install halted with tor.
```
2021-11-12 04:07:48 (10.0 MB...Raspi 4 4gb
Following instructions - https://docs.samourai.io/dojo/first-install with advanced config to allow for local bitcoind instance.
Ran `./dojo.sh install` as required. Install halted with tor.
```
2021-11-12 04:07:48 (10.0 MB/s) - 'go1.16.6.linux-amd64.tar.gz' saved [129049323/129049323]
go1.16.6.linux-amd64.tar.gz: OK
Cloning into '/usr/local/src/obfs4proxy'...
Note: checking out 'tags/obfs4proxy-0.0.11'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD is now at b5a9f3c Do the release ritual for obfs4proxy-0.0.11
/bin/sh: 1: go: Exec format error
The command '/bin/sh -c cd /usr/local/src && echo "$GOLANG_SHA256 *$GOLANG_ARCHIVE" > GO_CHECKSUMS && wget "$GOLANG_DL_URL/$GOLANG_ARCHIVE" && sha256sum -c GO_CHECKSUMS 2>&1 | grep OK && tar -C /usr/local/lib -xzf "$GOLANG_ARCHIVE" && ln -s /usr/local/lib/go/bin/go /usr/local/bin/ && git clone "$OBFS4_URL" /usr/local/src/obfs4proxy && cd obfs4proxy && git checkout "tags/obfs4proxy-$OBFS4_VERSION" && go build -o obfs4proxy/obfs4proxy ./obfs4proxy && cp ./obfs4proxy/obfs4proxy /usr/local/bin && cd .. && rm "$GOLANG_ARCHIVE" && rm -rf obfs4proxy' returned a non-zero code: 2
ERROR: Service 'tor' failed to build : Build failed
```https://code.samourai.io/dojo/samourai-dojo/-/issues/151Add scheme and port back to keyserver URI in bitcoin Dockerfile2022-02-04T21:57:33ZJustin CAdd scheme and port back to keyserver URI in bitcoin DockerfileWhen updating dojo, I was getting a failure in the bitcoind Dockerfile with message: `gpg: keyserver receive failed: Server indicated a failure`. I was able to get past the error by adding the full keyserver URI which included the scheme...When updating dojo, I was getting a failure in the bitcoind Dockerfile with message: `gpg: keyserver receive failed: Server indicated a failure`. I was able to get past the error by adding the full keyserver URI which included the scheme and port, i.e. `hkp://keyserver.ubuntu.com:80` and `hkp://keys.openpgp.org:80`.https://code.samourai.io/dojo/samourai-dojo/-/issues/150installation on synology2021-10-19T14:42:23ZBTC Davidinstallation on synologyHi,
I'm installing Dojo on Synology following the documentation: [link](https://code.samourai.io/ronindojo/samourai-dojo/-/blob/a2b63de60be86c7dd297865d7e285ccf74d630cf/doc/DOCKER_setup.md#install)
After running sudo ./dojo.sh install
...Hi,
I'm installing Dojo on Synology following the documentation: [link](https://code.samourai.io/ronindojo/samourai-dojo/-/blob/a2b63de60be86c7dd297865d7e285ccf74d630cf/doc/DOCKER_setup.md#install)
After running sudo ./dojo.sh install
The installer stops at the point where it wants to install Tor service. It throughs the following exception:
![image](/uploads/7347fa1ab6cd0ce128a164dedc02e6ba/image.png)
Could you create a fix or please help me install?
Thanks!
Keep up the good work!https://code.samourai.io/dojo/samourai-dojo/-/issues/149Importer Exception while Import big transaction history2021-10-20T16:38:58ZChuck NorrisonImporter Exception while Import big transaction history### Issue found
The Importer will crash with an exception if a wallet gets imported with a large history
> "error":"failed to get confirmed status"
![image](/uploads/cc26979916242242d7a9b8ff69bcfb59/image.png)
### Test
To reproduce ...### Issue found
The Importer will crash with an exception if a wallet gets imported with a large history
> "error":"failed to get confirmed status"
![image](/uploads/cc26979916242242d7a9b8ff69bcfb59/image.png)
### Test
To reproduce just add a big wallet to sentinel and watch the dojo logs.
### Conclusion
To overcome this limitation i found a config for this, search for `NODE_ADDR_FILTER_THRESHOLD`. Default is a history of 1000. This was not successful after increasing it to 20000.
So this is not really an issue, more a hidden filter?
### Improvement
To get this improved, the wallets like sentinel or samourai needs to get notice of the import process and maybe a notification when its done. To get out the hidden filter value to the user in some way would be great.
The Samourai Wallet User should be notified if his history exceeds supported length, this is criticalhttps://code.samourai.io/dojo/samourai-dojo/-/issues/148No funds on paired wallet2021-10-20T16:33:22ZChuck NorrisonNo funds on paired walletAfter setup my dojo from release v1.11.0 and synced some days, all check marks are in green state on my Dojo Maintenance Tool. Beside some errors i can observe in the logs everything seems to work basically. So i paired an existent walle...After setup my dojo from release v1.11.0 and synced some days, all check marks are in green state on my Dojo Maintenance Tool. Beside some errors i can observe in the logs everything seems to work basically. So i paired an existent wallet to my Dojo, but it ends up witout any balance. My PayNym shows up, but my wallet data are missing entirely.
Configuration of my dojo is default and very basic as recommended. So iam running the local_bitcoind indexer.
Would be glad to get in some ideashttps://code.samourai.io/dojo/samourai-dojo/-/issues/147Docker Memory Use Windows 102021-03-04T09:56:14ZNathan JenkinsDocker Memory Use Windows 10Just a small documentation thing, if users are trying to run Samourai within a Docker container on Windows 10 they will need to create %HOMEPATH%/.wslconfig with the following lines:
[wsl2]
memory=4GB # Where 4 GB < total system memory
...Just a small documentation thing, if users are trying to run Samourai within a Docker container on Windows 10 they will need to create %HOMEPATH%/.wslconfig with the following lines:
[wsl2]
memory=4GB # Where 4 GB < total system memory
Finally they will have to run **Restart-Service LxssManager** from an administrative PowerShell.https://code.samourai.io/dojo/samourai-dojo/-/issues/146indexer build falure?2021-03-03T15:52:21ZSteve Mabbuttindexer build falure?First time install on Ubuntu 20.04.2 LTS 64-bit, AMD Ryzen 7, 64 GB RAM
Following steps https://docs.samourai.io/en/dojo/first-install, to
> ./dojo.sh install
fails with
```
Step 14/16 : RUN cd "$INDEXER_HOME/addrindexrs" && ...First time install on Ubuntu 20.04.2 LTS 64-bit, AMD Ryzen 7, 64 GB RAM
Following steps https://docs.samourai.io/en/dojo/first-install, to
> ./dojo.sh install
fails with
```
Step 14/16 : RUN cd "$INDEXER_HOME/addrindexrs" && cargo install --path .
---> Running in 74ebf16c8b52
Installing addrindexrs v0.3.0 (/home/indexer/addrindexrs)
Updating crates.io index
error: failed to compile `addrindexrs v0.3.0 (/home/indexer/addrindexrs)`, intermediate artifacts can be found at `/home/indexer/addrindexrs/target`
Caused by:
cyclic package dependency: package `cc v1.0.41` depends on itself. Cycle:
package `cc v1.0.41`
... which is depended on by `generator v0.6.24`
... which is depended on by `loom v0.4.0`
... which is depended on by `crossbeam-utils v0.8.2`
... which is depended on by `crossbeam-epoch v0.9.2`
... which is depended on by `crossbeam-deque v0.8.0`
... which is depended on by `rayon v1.5.0`
... which is depended on by `cc v1.0.41`
... which is depended on by `secp256k1 v0.15.5`
... which is depended on by `bitcoin v0.21.0`
... which is depended on by `addrindexrs v0.3.0 (/home/indexer/addrindexrs)`
ERROR: Service 'indexer' failed to build: The command '/bin/sh -c cd "$INDEXER_HOME/addrindexrs" && cargo install --path .' returned a non-zero code: 101
Attaching to
```
Any suggestions? Thanks!https://code.samourai.io/dojo/samourai-dojo/-/issues/145Add Bitcoind Wallet Configuration to Docker Template2022-09-13T17:02:57ZBetty von SchmartenhausenAdd Bitcoind Wallet Configuration to Docker TemplateIs it possible to have the option to enable the wallet functionality in *docker-bitcoind.conf.tpl* so that the wallet can be toggled on or off without having to edit *restart.sh* in the bitcoind Docker container. This would survive upgra...Is it possible to have the option to enable the wallet functionality in *docker-bitcoind.conf.tpl* so that the wallet can be toggled on or off without having to edit *restart.sh* in the bitcoind Docker container. This would survive upgrades of Dojo. AFAICT this looks a matter of simply updating *bitcoind_options* in *restart.sh* such that *-disablewallet=0* becomes something like *-disablewallet=$BITCOIND_DISABLE_WALLET* which is then configurable in the Docker template file.
This of course depends on whether having the wallet enabled is something you want to support given SW doesn't need it. It does mean however that users can get other solutions working with their Dojo full node.
-- BVShttps://code.samourai.io/dojo/samourai-dojo/-/issues/144Synology setup broken2020-10-20T06:14:48ZDanSynology setup brokenI am trying to install Dojo on a Synology device. DSM version: 6.2.3-25426 Update 2
I followed the instructions here: https://code.samourai.io/dojo/samourai-dojo/-/blob/master/doc/DOCKER_synology_setup.md
Once the docker containers sta...I am trying to install Dojo on a Synology device. DSM version: 6.2.3-25426 Update 2
I followed the instructions here: https://code.samourai.io/dojo/samourai-dojo/-/blob/master/doc/DOCKER_synology_setup.md
Once the docker containers start to boot, I get a large number of Permission denied errors.
A few examples:
tor | /bin/bash: /restart.sh: Permission denied
whirlpool | /bin/bash: /restart.sh: Permission denied
explorer | /bin/bash: /home/node/app/restart.sh: Permission denied
I believe this is due to how the images create users and groups. I have seen other issues with users created in Docker images not working on Synology. I believe the custom user management system on Synology does not play well with this sort of design.https://code.samourai.io/dojo/samourai-dojo/-/issues/143Automatically switch to a Tor mirror if download of Tor code from Tor website...2020-09-26T12:36:15ZLaurentMTAutomatically switch to a Tor mirror if download of Tor code from Tor website fails