Docker compose setup failing with error on controller

1

Is there an issue with the "complicated" docker compose quickstart from the page below at the moment?

Ive tried installing it again locally and it keeps failing at this point below. Ive also started from scratch on a new VM and it fails at the same point:

ziti-controller-1 | PKI generated successfully
ziti-controller-1 |
ziti-controller-1 |
ziti-controller-1 | /persistent/ziti-edge-controller.yaml doesn't exist. Generating config file
ziti-controller-1 |
ziti-controller-1 | adding controller root CA to ca bundle: /persistent/pki/ziti-controller-root-ca/certs/ziti-controller-root-ca.cert
ziti-controller-1 | adding signing root CA to ZITI_PKI_CTRL_CA: /persistent/pki/cas.pem
ziti-controller-1 | wrote CA file to: /persistent/pki/cas.pem
ziti-controller-1 | adding parent intermediate CA to ZITI_PKI_SIGNER_CERT: /persistent/pki/signing.pem
ziti-controller-1 | adding grandparent intermediate CA to ZITI_PKI_SIGNER_CERT: /persistent/pki/signing.pem
ziti-controller-1 | wrote signer cert file to: /persistent/pki/signing.pem
ziti-controller-1 | Controller configuration file written to: /persistent/ziti-controller.yaml
ziti-controller-1 | [ 0.009] FATAL ziti/controller/subcmd.configureController: {error=[unable to load identity (open /persistent/pki/ziti-controller-intermediate/certs/ziti-controller-client.chain.pem: no such file or directory)]} could not read configuration file [/persistent/ziti-controller.yaml]
ziti-controller-1 | --- There was an error while initializing the controller ---
col@doc1:~/Desktop/docker$

This has worked fine for me in the past - am I missing something here or is there a way to clear the error to continue ?

2

Ive just tried with the simplified docker compose file and having the same issue .....

Looking at the discourse posts I found this which mentions similar errors im getting - i followed the steps outlined in it but still get same issue:

3

I'll try it out. It's possible that a recent update caused it to fail.

4

Yep. I was able to replicate the issue with the latest set of containers. I'll see if I can tweak the compose to allow it to function. If not, we'll need to dig in and find out how to get the example back working.

5

Thanks for verifying - been driving me crazy for past few hours !

6

Easiest and quickest will be to use a version that works. In your .env file change ${ZITI_VERSION} .

Set it to to v1.1.11 for the timebeing and you'll be back running...

ZITI_VERSION=v1.1.11
7

Brillant, have to step away for a bit so will try that later, Cheers

8

Cheers, back online, i'll keep an eye out for the updated latest config

9

I published container image openziti/quickstart:1.1.11 (and :latest) with fixes.

1 Like