illuminatus
illuminatus
> > but would potentially use the same logic for all non cnode.sh scripts anyway. T > > @TrevorBenson - On contrary, I'd argue their healthchecks are actually different (eg:...
> > For checking tip on cncli or dbsync, I would suggest not using koios, but instead relying on the node query tip. This way if the node isn't syncing...
> ipv6 support in the netavark dhcp proxy is not implemented so this is expected for now @Luap99 Is this still the case today?
> In that case, the throughput computed is not just “within a factor of 2 or so”, but it can be many times the bandwidth of the link. I think...
This might relate to #1010 which seems to reference Docker containers quite often and the stop should also be receiving a SIGKILL event. Although, I'm unsure if the volatile data...
I took a closer look at the code for dockerTools.buildImage and realized I had overlooked `config` as a method to add **any** instruction to the build. Unless keeping the `${dbSyncScript.name}`...
> This looks good to me. I'll do a bit of testing in the meantime. PS: It looks like you need to set up [commit signing](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). New laptop, I must...
@sgillespie Commit is now signed.
FWIW Here is my preview network pool, and cncli containers showing healthy once the script was copied in and healthcheck interval was reached: ``` # podman ps --filter 'name=preview-cncli-[slv]' --filter...
> Looks good! How I have tested... > > cp the script into cncli sync, validate, leaderlog, pt-send-slots, pt-send-tip containers > > Execute the script with docker exec. > >...