Works properly for me. I think your suspicion about the .env is correct;
it is probably not considered when checking whether something has
changed, so docker juse re-uses the previous image.
On 4/13/2021 9:51 PM, Flavio Pompermaier wrote:
Hi Chesnay,
my tests were done using docker-compose (wi
Hi Chesnay,
my tests were done using docker-compose (with the command 'docker-compose
up --build -d flink-jobmanager flink-taskmanager').
These are the necessary files (./flink/db-libs/* contains the jdbc
libraries I use while /opt/flink/data is used as a volume to share files
with other dockers):
Please provide steps to reproduce the issue.
I can't see anything wrong in the dockerfiles (they reference the
correct release url), and the referenced release correctly identifies
itself as 1.11.3 .
I also started a container with the image, started a jobmanager, and the
logs show 1.11.3 like
Hi to all,
I've just build a docker that use the image flink:1.11.3-scala_2.12-java11
but the web UI (and logs too) display Flink 1.11.2 (Commit: fe36135). Was
there an error with the release?
Best,
Flavio
