Docker image startup issue

[Daennes]

Hello,
I have upgraded from version 9 to 10 which is causing a startup problem. Tested it with both my existing setup and a clean docker state setup.
Used unmodified Docker compose file to spin up the services.

Tested on Ubuntu 20.04 and MacOS 11.4

/run/secrets
Generating PGPASS file
Connecting to network: mainnet
/nix/store/xirfrf8q9kdj2hjcfrwbqwv7qhip0nnz-entry-point/bin/entry-point: line 26: /nix/store/3pvccdbrmaih10f6xf1csm1fjrsy72w2-cardano-db-sync-mainnet: Is a directory
/nix/store/xirfrf8q9kdj2hjcfrwbqwv7qhip0nnz-entry-point/bin/entry-point: line 26: exec: /nix/store/3pvccdbrmaih10f6xf1csm1fjrsy72w2-cardano-db-sync-mainnet: cannot execute: Is a directory

[tobg]

Same issue here

[erikd]

This was fixed in #690 . Unfortunately that did not make the 10.0.0 release, but the docker-compose.yaml file can be copied from master.

[vbonini]

Continuing the failing startup discussion:

I had the same issue. I deployed the master image but get a new error. For reference I'm trying to use non-extended service.

Please let me know if you want me to open a new issue for this.

/run/secrets
Generating PGPASS file
Connecting to network: mainnet
cardano-db-sync-extended: FatalError {fatalErrorMessage = "Error parsing node config: AesonException \"Error in $: key \\\"AlonzoGenesisFile\\\" not found\""}

[erikd]

@vbonini master is updated almost daily. The error you see is because master has code for the upcoming Alonzo release and your version of the node does not support Alonzo.

Users should avoid master and should only use tagged releases.

[vbonini]

Thank you for the confirmation.

So we are using K8s for our deployment, and pulled the 10.0.0 image when we saw the original issue. I can recreate and plug in the modified file in #690 if I need to. Where should that data go?

Never mind, I am implementing a workaround with the entry-point.

[erikd]

I have asked the release manager if we should do a release just to fix this docker issue.

[erikd]

There will be a 10.0.1 release.