Hi,
That's because the ConfigMap volume is always read-only.
Currently /docker-entrypoint.sh will try to update some configs in docker
Environment. But these are not needed in kubernetes.
So I think we can ignore those errors safely when using the operator/native
kubernetes integration.
There is
I’ve noticed that all jobs I start with `flink-operator` have the following
message at the top of their logs for both jobmanager and taskmanager pods:
```
sed: couldn't open temporary file /opt/flink/conf/sedRTwsr1: Read-only file
system
sed: couldn't open temporary file /opt/flink/conf/sedcDS3
