madMAx43v3r / chia-gigahorse

221 stars 31 forks source link

Updating docker from giga21 to giga22 #227

Closed darkenbula closed 11 months ago

darkenbula commented 11 months ago

When attempting to update my docker past 1.8.2.giga21-nvidia the harvester will attempt to resync the chain from scratch again.

Rolling back to giga22 will fix the issue each time, will try to get some more detailed logs when i get back from work

docker run -d --name='Chia-Madmax-NVIDIA' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRaid" -e HOST_CONTAINERNAME="Chia-Madmax-NVIDIA" -e 'NVIDIA_VISIBLE_DEVICES'='GPU-2c8cd41b-4bf5-73dc-1eff-96d27d64113b' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='/mnt/user/appdata/chia-madmax-nvidia/logo.png' -v '/mnt/cache/appdata/chia-madmax-nvidia/':'/data':'rw' -v '/mnt/user/chia':'/unraid_chia':'rw' -v '/mnt/disks':'/netapp':'rw' --runtime=nvidia 'ghcr.io/madmax43v3r/chia-gigahorse:1.8.2.giga21-nvidia'

darkenbula commented 11 months ago

If i change my docker run to the following

docker run -d --name='Chia-Madmax-NVIDIA' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRaid" -e HOST_CONTAINERNAME="Chia-Madmax-NVIDIA" -e 'NVIDIA_VISIBLE_DEVICES'='GPU-2c8cd41b-4bf5-73dc-1eff-96d27d64113b' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='/mnt/user/appdata/chia-madmax-nvidia/logo.png' -v '/mnt/cache/appdata/chia-madmax-nvidia/':'/data':'rw' -v '/mnt/user/chia':'/unraid_chia':'rw' -v '/mnt/disks':'/netapp':'rw' --runtime=nvidia 'ghcr.io/madmax43v3r/chia-gigahorse:1.8.2.giga22-nvidia'

Nothing further is generated in the log file, but running show -s gives

Network: mainnet Port: 8444 RPC Port: 8555 Node ID: 7372674f9d8a1d46ab80167853757978bb63658957c5336a4742a4be12820337 Genesis Challenge: ccd5bb71183532bff220ba46c268991a3ff07eb358e8255a65c30a2dce0e5fbb

Searching for an initial chain

You may be able to expedite with 'chia peer full_node -a host:port' using a known node.

Blockchain has no blocks yet

darkenbula commented 11 months ago

nevermind. read the manual and found docker paths have changed.