Is console.address hardcoded in docker image?

[EddieA]

@alpharabbit

Using “Install via YAML” is way better in my opinion.

Care to share, or point folks to, your HowTo.

[Alexey]

I found a reason. They didn’t update the base image hardcoded in their application.
The /entrypoint is the old one before it has been changed to preserve binaries to do not redownload them every time.
The old one has this line:

...
SNO_RUN_PARAMS="${RUN_PARAMS} --console.address=:14002"
...

instead of

@elek

: ${STORJ_CONSOLE_ADDRESS:=0.0.0.0:14002}
export STORJ_CONSOLE_ADDRESS
          

To override this you need to pass a command line argument --console.address=:14004 after the image name, but there is no option in their app to do that.
So there is no way to use a custom console port in this app and you need to use the Create app from the docker-compose.yaml file feature instead of this app.