-
Notifications
You must be signed in to change notification settings - Fork 33
Description
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"]