Skip to content

Dockerfile and entry point issues on openshift image based deployments #85

@rabay108

Description

@rabay108

POD did not get started due to this issue in the POD logs - Error: failed to read and merge config files: failed to read config $CONFIG_PATH: open $CONFIG_PATH: no such file or directory

The reason your ENTRYPOINT could be failing may be due to Docker behavior: The "Exec Form" of ENTRYPOINT (using square brackets []) does not expand environment variables.
When you write ["/openshift-mcp-server", "--config", "$CONFIG_PATH"], the container looks for a literal file on disk named exactly $CONFIG_PATH (dollar sign and all). It does not look for the value /mcp_config.toml

The following change worked for me ENTRYPOINT ["/bin/sh", "-c", "exec /openshift-mcp-server --config $CONFIG_PATH"]
I also see ENTRYPOINT /openshift-mcp-server --config $CONFIG_PATH might work removing square brackets
OR by hardcoding ENTRYPOINT ["/openshift-mcp-server", "--config", "/mcp_config.toml"]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions