Well done for getting this solved! Looking at the logs, I gather you used docker-compose on this host awhile ago, and then just come back to it, updated the docker-compose and ran into this trap?!. I am thinking this because of
in particular, this part /openziti/. A few months ago, there was a breaking change for the docker-compose environment, and a rejig of locations. /openziti no longers exists, and it is now /persistent. This was done for a couple of reasons, but the major one was because updating the container DID NOT update the binary components (well it did in the container, but they were referencing the old one in the /openziti volume.
For completeness, Geoff put instructions here: Bump on openziti docker images please - #10 by gberl002 on how to migrate.
@TheLumberjack think we should update the documentation with reference to this change to help anyone else who might come across this.
So, in your case, removing the docker volume (docker volume rm ziti-fs) would have most likely resolved the problem (meant starting from fresh), or having the article available could have meant fixing up without having to start at ground zero.
Either way, great job!