rafaribe
commented
2 years ago You don't even have to build the container yourself if you don't want to. There's already pre-containers built on GitHub Container Registry and DockerHub.
Here's the relevant part of my docker-compose that I use:
helium_workarounds:
image: ghcr.io/heliumdiy/helium_workarounds:latest
container_name: helium_workarounds
volumes:
- /home/pi/miner_data/log:/log
- /var/run/docker.sock:/var/run/docker.sock
environment:
- LOG_ONLY_FAILED=True
networks:
- helium
restart: unless-stopped
logging:
driver: json-file
options:
tag: "{{.ImageName}}|{{.Name}}|{{.ImageFullID}}|{{.FullID}}"The entrypoint of the container expects the file to be supplied either by ENV var or as the first argument. Here are the relevant lines to solve your problem: https://github.com/HeliumDIY/helium_workarounds/blob/main/Dockerfile#L13 https://github.com/HeliumDIY/helium_workarounds/blob/main/src/fix_not_found_peer.py#L56 https://github.com/HeliumDIY/helium_workarounds/blob/main/src/fix_not_found_peer.py#L58
OmegxEU
serbyxp
n8091977
benisdev-py
hi, I'm not very failure with any sort of connecting 2 docker containers together,
I have downloaded the repo and ran docker build helium_workaround -t wa docker run wa I get a :
Traceback (most recent call last): file "fix_not_found_peer.py, line 67, in
for line in follow(log_file):
File "fix_not_found_peer.py, line 17, in follow
File = open(filename, 'r')
FileNotFoundError: [Errno 2] no such file or directory /log/console.log'
I sure in the docker run wa I need to add some sort of bind or mount command to the helium miner docker folder...
assuming the docker helium miner container is the standard repo with a var/data folder bind to / home/pi/hotspot_data would I need to add a ---mount type=bind,source=/home/pi/hotspot_data,target=/var/data <<< or /var/data/log