Has anyone seen the operator fail to bring up customized Docker containers? I'm down the following Dockerfile

FROM flink:1.17.1

and when run using the operator, it's crashing with:

/usr/bin/sed: couldn't open temporary file /opt/flink/conf/sedpkIp5Z: Read-only file system
/usr/bin/sed: couldn't open temporary file /opt/flink/conf/sedwSRucU: 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
[ERROR] The execution result is empty.
[ERROR] Could not get JVM parameters and dynamic configurations properly.
[ERROR] Raw output from BashJavaUtils:
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.

Are you using a custom entrypoint? This post might help - https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/issues/213

To the best of my understanding I shouldn't be but I'll take a look. In theory it should be the same as the "default" entrypooint provider by the flink container.

You can ignore those

Read-only file system

errors. It seems your modifications to the docker containers broke Flink'

bash-java-utils.jar

. Check the

flink-dist/src/main/flink-bin/bin/config.sh

which is emitting the

[ERRRO]

messages you are seeing

I'll take a look. I do find it a bit odd that doing a docker build with no new layers seems to break the container.

I agree, that shouldn't happen. I wonder if some env variables are not visible / overridden ?

Yes, I am.

Possible. I have no experience with that

Luckily, the issue that Ravi found has a workaorund. I'm going to try to dig into this today a bit more and if I find a fix get a patch together.