Open unintended-consequences opened 1 year ago
Have tried mapping known_hosts to:
/etc/ssh /root/.ssh
Docker container itself works as I can get the file_log_consumer to run. But the network_log_consumer is not a happy bunny.
@unintended-consequences your server is already in your known_hosts file?
@unintended-consequences this is docker-compose.yml that works for me
version: "3"
services:
chiadog:
image: 'ghcr.io/martomi/chiadog:latest'
container_name: chiadog
volumes:
- ~/.config/chiadog/:/root/.chiadog/
- ~/.chia/mainnet/log/:/root/.chia/mainnet/log:ro
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
You should add a "How to run with Docker" section to the README
I'm trying to spin up a new instance via docker-compose. There doesn't seem to be much documentation.
Have tried the following:
I've put a config.yaml into the config folder but I am getting this error:
Which suggests I need to feed the docker some SSH keys?