Problem to solve
The entrypoint currently used by the evm-single docker image is defined here:
https://github.com/rollkit/rollkit/blob/main/apps/evm/single/entrypoint.sh
It hardcodes a number of flags which may or may not be required (?), this is slightly unclear to me.
I would like to pass custom flags (e.g. to override rpc listen address) without having to override the entire entrypoint script.
Proposed solution or feature
Generally, the expectation would be that the entrypoint executes the evm-single binary as its entrypoint passing: $@
This allows consumers in docker compose setups to customise their start options via the command definition in a compose service, and pass arbitrary flags which take precedence over default config opts..etc
For example: when I run docker run ghcr.io/celestiaorg/celestia-app I see the command help output from the celestia-appd binary, as this is the default entrypoint.
Alternatives considered
No response
Additional context
No response
Problem to solve
The entrypoint currently used by the
evm-singledocker image is defined here:https://github.com/rollkit/rollkit/blob/main/apps/evm/single/entrypoint.sh
It hardcodes a number of flags which may or may not be required (?), this is slightly unclear to me.
I would like to pass custom flags (e.g. to override rpc listen address) without having to override the entire entrypoint script.
Proposed solution or feature
Generally, the expectation would be that the entrypoint executes the
evm-singlebinary as its entrypoint passing:$@This allows consumers in docker compose setups to customise their start options via the
commanddefinition in a compose service, and pass arbitrary flags which take precedence over default config opts..etcFor example: when I run
docker run ghcr.io/celestiaorg/celestia-appI see the command help output from thecelestia-appdbinary, as this is the default entrypoint.Alternatives considered
No response
Additional context
No response