[ 
https://issues.apache.org/jira/browse/FLINK-29145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arseniy Tashoyan updated FLINK-29145:
-------------------------------------
    Description: 
When running a FlinkDeployment, we can see error messages:
{code:none}
sed: couldn't open temporary file /opt/flink/conf/sedHIUGh6: Read-only file 
system
sed: couldn't open temporary file /opt/flink/conf/sedNALzes: Read-only file 
system
/docker-entrypoint.sh: line 73: /opt/flink/conf/flink-conf.yaml: Read-only file 
system
/docker-entrypoint.sh: line 89: /opt/flink/conf/flink-conf.yaml.tmp: Read-only 
file system
{code}
The script _docker-entrypoint.sh_ tries to modify some settings in 
{_}flink-conf.yaml{_}, despite this config file is mounted read-only from a 
ConfigMap.

Such on-the-fly config modifications make no sense for deployments in 
Kubernetes. Instead we specify Flink settings via the _flinkConfiguration_ 
setting in the FlinkDeployment descriptor.

In addition, _docker-entrypoint.sh_ tries to modify a deprecated setting 
{_}query.server.port{_}:
{code:bash}
set_config_option query.server.port 6125
{code}
The setting query.server.port is deprecated in favor of 
{_}queryable-state.server.ports{_}:
[https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/queryable_state/#state-server]

  was:
When running a FlinkDeployment, we can see error messages:

{code:none}
sed: couldn't open temporary file /opt/flink/conf/sedHIUGh6: Read-only file 
system
sed: couldn't open temporary file /opt/flink/conf/sedNALzes: Read-only file 
system
/docker-entrypoint.sh: line 73: /opt/flink/conf/flink-conf.yaml: Read-only file 
system
/docker-entrypoint.sh: line 89: /opt/flink/conf/flink-conf.yaml.tmp: Read-only 
file system
{code}

The script _docker-entrypoint.sh_ tries to modify some settings in 
_flink-conf.yaml_, despite this file mounted read-only from a ConfigMap.

Such on-the-fly config modifications make no sense for deployments in 
Kubernetes. Instead we specify Flink settings via the _flinkConfiguration_ 
setting in the FlinkDeployment descriptor.

In addition, _docker-entrypoint.sh_ tries to modify a deprecated setting 
_query.server.port_:

{code:bash}
set_config_option query.server.port 6125
{code}

The setting query.server.port is deprecated in favor of 
_queryable-state.server.ports_:
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/queryable_state/#state-server



> docker-entrypoint.sh - Read-only file system
> --------------------------------------------
>
>                 Key: FLINK-29145
>                 URL: https://issues.apache.org/jira/browse/FLINK-29145
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>            Reporter: Arseniy Tashoyan
>            Priority: Major
>
> When running a FlinkDeployment, we can see error messages:
> {code:none}
> sed: couldn't open temporary file /opt/flink/conf/sedHIUGh6: Read-only file 
> system
> sed: couldn't open temporary file /opt/flink/conf/sedNALzes: Read-only file 
> system
> /docker-entrypoint.sh: line 73: /opt/flink/conf/flink-conf.yaml: Read-only 
> file system
> /docker-entrypoint.sh: line 89: /opt/flink/conf/flink-conf.yaml.tmp: 
> Read-only file system
> {code}
> The script _docker-entrypoint.sh_ tries to modify some settings in 
> {_}flink-conf.yaml{_}, despite this config file is mounted read-only from a 
> ConfigMap.
> Such on-the-fly config modifications make no sense for deployments in 
> Kubernetes. Instead we specify Flink settings via the _flinkConfiguration_ 
> setting in the FlinkDeployment descriptor.
> In addition, _docker-entrypoint.sh_ tries to modify a deprecated setting 
> {_}query.server.port{_}:
> {code:bash}
> set_config_option query.server.port 6125
> {code}
> The setting query.server.port is deprecated in favor of 
> {_}queryable-state.server.ports{_}:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/queryable_state/#state-server]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to