Bug Run in ./private-tangle.sh install #88
Description
Bug description
Briefly describe the bug.
Docker and docker-compose version
Which version of Docker and docker-compose are you running?
- Docker version:
pi@raspberrypi:~ $ docker --version
Docker version 24.0.6, build ed223bc
pi@raspberrypi:~ $ sudo apt install docker-compose
Lendo listas de pacotes... Pronto
Construindo árvore de dependências... Pronto
Lendo informação de estado... Pronto
docker-compose is already the newest version (1.25.0-1).
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libfuse2 tini
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
pi@raspberrypi:~ $ docker-compose --version
docker-compose version 1.29.2, build unknown
Hardware specification
What hardware are you using?
- Operating system:
Raspberry pi 4 Model 4 4GB
Steps To reproduce the bug
Explain how the maintainer can reproduce the bug.
Based on the provided information, here's how the bug can be reproduced:
Steps To reproduce the bug
-
Environment Setup:
- Use a Raspberry Pi with the same OS and environment as yours.
- Ensure that Python 3.9 is installed along with the required packages (
urllib3,requests,docker, etc.). - Install Docker and Docker Compose on the Raspberry Pi.
-
Clone the Repository:
- Clone the
one-click-tanglerepository into the home directory of the Raspberry Pi:cd ~/ git clone [repository_url] one-click-tangle
- Clone the
-
Navigate to the Hornet Private Net Directory:
- Change the directory to
hornet-private-netwithin theone-click-tanglerepository:cd ~/one-click-tangle/hornet-private-net
- Change the directory to
-
Run the Installation Script:
- Execute the
private-tangle.shscript with theinstallargument:./private-tangle.sh install
- Execute the
-
Observe the Errors:
- After running the script, you should observe the errors mentioned in your initial message, starting with the
digcommand not found and followed by the connection errors related to Docker.
- After running the script, you should observe the errors mentioned in your initial message, starting with the
Note: The exact reproduction might vary depending on the specific environment configurations, installed packages, and other factors. The maintainer might need to ensure that the environment closely matches yours to reproduce the bug accurately.
Expected behaviour
You expected the ./private-tangle.sh install command to successfully install and set up a private Tangle using the Hornet node software. This would involve initializing necessary configurations, starting up the required containers, and ensuring that all dependencies and services are running properly.
Actual behaviour
When you executed the ./private-tangle.sh install command, several errors occurred:
The dig command was not found, as indicated by the error message ./private-tangle.sh: linha 26: dig: comando não encontrado.
There was an issue with the Python script trying to make a connection, which resulted in a ConnectionRefusedError: [Errno 111] Connection refused.
This connection issue cascaded into multiple other errors, all stemming from the inability to establish a connection. The primary issue seems to be related to the Docker service, as indicated by the error messages related to docker/transport/unixconn.py and docker.errors.DockerException.
Errors
./private-tangle.sh: linha 26: dig: comando não encontrado: This error indicates that the dig command, which is commonly used for DNS lookup operations, is not available on your system.
ConnectionRefusedError: [Errno 111] Connection refused: This error suggests that the Python script tried to establish a connection (likely to a Docker service or container) but was unable to do so because the connection was refused.
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')): This error, stemming from the Python urllib3 library, further confirms the connection issue.
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')): This error from the Python requests library is another manifestation of the connection problem.
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(111,'Connection refused')): This error indicates that the script was unable to fetch the Docker server API version due to the connection being refused.