is it?

Does this fix https://github.com/SumoLogic/sumologic-collector-docker/issues/103 ? Looks like image still using apt instead of apk for alpine too

seeing the same issues with `ubuntu:22.10` as there are many vulnerabilities in that ubuntu:18 base image, can we get an update on this?

We've restarted the orchestrator client a few times now, the round the process believes it's attempting to claim with seems to be wrong given the status it outputs, and it's...

This seems likely related: https://github.com/livepeer/go-livepeer/issues/2661

> > current round is not initialized > > This sounds very weird. Which network do you use, `arbitrum-one-mainnet`? Yes we use `arbirtum-one-mainnet`

We're still seeing these logs with v0.5.37 ``` HTTP Response Error 500: Error calling reward: execution reverted: current round is not initialized ``` Any ideas?