Internal/External
External
Area
Other (cardano-submit-api / Docker image packaging)
Summary
The ghcr.io/intersectmbo/cardano-submit-api:10.6.2 up to 11.0.1 images crash-loops on
startup and never begins listening. On boot the container immediately exits with:
cardano-submit-api: AesonException "Error in $: key "Options" not found"
This is a config-parse failure: the config bundled in / selected by the image's
mainnet-based entrypoint is missing a field the binary in this tag now requires,
so the two are out of sync within the same published image. As a result the
submit-api never binds its port.
The previous tag we ran started cleanly with an identical compose configuration (10.5.2);
only the image tag changed.
Steps to reproduce
-
Run the image with only the network selector, e.g.:
docker run --rm \
-e NETWORK=mainnet \
-v /path/to/node-ipc:/node-ipc \
ghcr.io/intersectmbo/cardano-submit-api:<TAG>
(or via docker compose with environment: [NETWORK=mainnet] and the
node socket mounted — no custom config supplied).
-
Observe the container exit immediately.
-
Check docker logs <container>:
cardano-submit-api: AesonException "Error in $: key "Options" not found"
Expected behavior
The image should start with a config that its own binary can parse, i.e. the
bundled/default config selected by NETWORK=mainnet should be valid for the
version in the same tag. Expected log output is the service binding on
0.0.0.0:8090 with no Aeson exception.
System info (please complete the following information):
- OS Name: Ubuntu
- OS Version: 24.04
- Image: ghcr.io/intersectmbo/cardano-submit-api:10.6.4 up to 11.0.1
- Host arch: x86_64
Additional context
Downgrading to the previously-working image tag (10.5.2) with the same
compose file resolves the issue, which points at the image build/config bundle
for 10.6.4-11.0.1 rather than user configuration. Please confirm which config the
mainnet entrypoint selects for this tag and whether it matches the format the
bundled binary expects
Internal/External
External
Area
Other (cardano-submit-api / Docker image packaging)
Summary
The
ghcr.io/intersectmbo/cardano-submit-api:10.6.2up to 11.0.1 images crash-loops onstartup and never begins listening. On boot the container immediately exits with:
This is a config-parse failure: the config bundled in / selected by the image's
mainnet-based entrypoint is missing a field the binary in this tag now requires,so the two are out of sync within the same published image. As a result the
submit-api never binds its port.
The previous tag we ran started cleanly with an identical compose configuration (
10.5.2);only the image tag changed.
Steps to reproduce
Run the image with only the network selector, e.g.:
(or via docker compose with
environment: [NETWORK=mainnet]and thenode socket mounted — no custom config supplied).
Observe the container exit immediately.
Check
docker logs <container>:Expected behavior
The image should start with a config that its own binary can parse, i.e. the
bundled/default config selected by
NETWORK=mainnetshould be valid for theversion in the same tag. Expected log output is the service binding on
0.0.0.0:8090with no Aeson exception.System info (please complete the following information):
Additional context
Downgrading to the previously-working image tag (10.5.2) with the same
compose file resolves the issue, which points at the image build/config bundle
for 10.6.4-11.0.1 rather than user configuration. Please confirm which config the
mainnetentrypoint selects for this tag and whether it matches the format thebundled binary expects