You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "HYUNHOO KWON (Jira)" <ji...@apache.org> on 2021/05/23 15:08:00 UTC
[jira] [Commented] (FLINK-21383) Docker image does not play well
together with ConfigMap based flink-conf.yamls
[ https://issues.apache.org/jira/browse/FLINK-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350055#comment-17350055 ]
HYUNHOO KWON commented on FLINK-21383:
--------------------------------------
Any updates?
On native k8s application mode, I found the following error in the console logs.
{code:java}
sed: couldn't open temporary file /opt/flink/conf/sedFktect: Read-only file system
sed: couldn't open temporary file /opt/flink/conf/sed63dRsw: Read-only file system
/docker-entrypoint.sh: line 75: /opt/flink/conf/flink-conf.yaml: Read-only file system
sed: couldn't open temporary file /opt/flink/conf/sedrIpLLv: Read-only file system
/docker-entrypoint.sh: line 90: /opt/flink/conf/flink-conf.yaml.tmp: Read-only file system
bash: kubernetes-jobmanager.sh: command not found
{code}
> Docker image does not play well together with ConfigMap based flink-conf.yamls
> ------------------------------------------------------------------------------
>
> Key: FLINK-21383
> URL: https://issues.apache.org/jira/browse/FLINK-21383
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes, flink-docker
> Affects Versions: 1.11.3, 1.12.1, 1.13.0
> Reporter: Till Rohrmann
> Priority: Minor
> Labels: auto-deprioritized-major, usability
>
> Flink's Docker image does not play well together with ConfigMap based flink-conf.yamls. The {{docker-entrypoint.sh}} script offers a few env variables to overwrite configuration values (e.g. {{FLINK_PROPERTIES}}, {{JOB_MANAGER_RPC_ADDRESS}}, etc.). The problem is that the entrypoint script assumes that it can modify the existing {{flink-conf.yaml}}. This is not the case if the {{flink-conf.yaml}} is based on a {{ConfigMap}}.
> Making things worse, failures updating the {{flink-conf.yaml}} are not reported. Moreover, the called {{jobmanager.sh}} and {{taskmanager.sh}} scripts don't support to pass in dynamic configuration properties into the processes.
> I think the problem is that our assumption that we can modify the {{flink-conf.yaml}} does not always hold true. If we updated the final configuration from within the Flink process (dynamic properties and env variables), then this problem could be avoided.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)