tjb_altf4

Tagged releases (comprised of many commits) are the only ones that will trickle down to docker and OS specific releases (e.g. Windows GUI client).

@Squid do you have a sample script for adding dockerhub credentials ? Or is this making its way to the GUI anytime soon ?

S to skip is what you want. As long as the chia has picked up the mnemonic correctly (shows in docker logs), you're all good

I eventually found that I needed to run the command in the script as background task so the jobs could overlap. Sorted.

You can filter and export to file using docker logs chia 2>&1 | grep ERROR > chia_log_error.txt The path to the containers full log can be found by running this command: docker inspect chia | grep log

log_stdout: true means it no longer sends logs to log/debug.log, but instead dockers logging mechanism itself (log icon on container) This is how you can view logs in console or simply "docker logs chia" if you want to see everything

OK this seems to be fine when using the drop down schedules (scheduled Hourly), but as soon I use a custom cron schedule the script won't restart until after the running script finishes. Is this a bug to be resolved, or is there a work around I need to use? Currently wanting to run the script every 30 min with: */30 * * * *

I've managed to solve my wallet not syncing issue by using the windows client in a VM and throwing a VPN client (PIA) to bypass all my current double NAT'd badness. Chia docker is still doing the hard work of harvesting, but now everything is synced up and working as normal in the windows client (pointing to chia smb share) I'm sure this can be done with docker networking, but I wanted a quick solution to tide me over.

For anyone that has moved logs to stdout and is having issues using grep on logs, this is the command you need: docker logs chia 2>&1 | grep YOURKEYWORD

Make sure you have port 8444 forwarded, if you know your ISP has CGNAT you might need a VPN as the double NAT my be causing the sync issues. I'm double NAT'd at the moment and have syncing issues with my wallet (only).

There is also an offical faucet now too, although the official is a once off use as far as I can tell. https://faucet.chia.net/

Should be on par, Linux versions in general are far better than windows by at least 10%, not sure if would be much between Linux distros. Unraid's strength for Chia farming is that it is already setup to manage the apps, the drives, and the tiered storage solution. If I happen to win a bingo coin (XCH), I'll probably build a dedicated farming rig with parts I have already. User scripts plugin (GUI for cron essentially) and at minimum this code running on a schedule is all you need to get going #!/bin/bash dirNew=$(date +"%H%M%m-%d%y") docker exec chia venv/bin/chia plots create -b 3840 -r 4 -n 1 -t /plotting/$dirNew -d /plots note "-it" has been removed (we don't want interactive mode), otherwise its the same as the normal docker command

You need to restart the container before the changes will kick in. I don't think those warnings are anything to be worried about, but read through this if you're worried about the health of you farm https://github.com/Chia-Network/chia-blockchain/wiki/Is-my-farm-healthy---I-am-not-finding-proofs

Are there any issues with overlapping jobs when scheduling? i.e. ~4hr jobs run every hour

@Partition Pixel it should be: ghcr.io/chia-network/chia:latest I updated yesterday, and I'm currently on 1.1.6.dev0 according chia version You should only need to press the check for updates button on docker page, if you want to force a check

Out of the box this docker isn't configured optimally for logging, after some research these are two changes I've made to get better logging. Both changes are made to the config.yaml file that will be in chia's appdata folder: change log_level to INFO (from WARNING) change log_stdout to true (from false) Change one adds more useful info to the logs, change two pushes the logs to the standard docker logging mechanism, which means it is visible from the GUI's log button. Happy hunting!

Looks like new image has been build, it should appear shortly. It is recommended to update as soon as you can.

No resume at the moment, so make sure your jobs have finished before you restart/update the container. note: this is a problem on all platforms, not docker specific

This document linked from their FAQ should give you a good idea https://www.chia.net/faq/#faq-8

My server is busy 24/7, so I don't use S3, so I cannot confirm either way.

Did CA settings get reset to default on a recent update ?

Sorry if this has been covered, but does the plugin work with multiple pools? Any gotchas? Thanks.

Try running the "detect" minimum PWM value again, or trying manually setting it higher.

For your distance, fiber is the appropriate choice, direct attach copper (DAC) is a cheap and effective alternative when dealing with short distances. This video should cover the rest.