Try to use the Exectuion Builder (v2) to build a EC for AP 5.10, but failed.

KNIME Business Hub
1

We built a new Execution Context (EC) Docker image and deployed it successfully in Kubernetes, but the executor cannot start and keeps restarting.

Observed Behavior

  • Executor pods continuously cycle (Creating → Running → Terminating).

  • The EC status remains Starting up and never becomes Ready.

  • The same deployment procedure works with another EC image.

Key Errors in Logs

The failing EC consistently shows these errors during KNIME startup:

java.io.FileNotFoundException:
/home/knime/knime/configuration/.../artifacts.xml (Permission denied)

followed by:

java.lang.IllegalStateException:
The platform metadata area could not be written:
/home/knime/knime-workspace/.metadata

What This Means

The KNIME runtime cannot write to its configuration and workspace directories:

/home/knime/knime/configuration
/home/knime/knime-workspace/.metadata

Because of this filesystem permission failure, the KNIME platform initialization aborts and the executor process exits.

Therefore the issue is not the path itself, but the write permissions or ownership of these directories in the failing Docker image/runtime.

I am trying to set up the HUB to test with potential customer (who has downloaded the latest AP, which is 5.10), but stuck here….. Please help, thank in advance.

1 Like
2

Hello,

Compare the working EC image and the failing one.

Check the USER in the Dockerfile that it is running as. Make sure it’s the right one (probably knime.)

Check ownership and mode inside the image:

  1. ls -ld /home/knime
  2. ls -ld /home/knime/knime
  3. ls -ld /home/knime/knime/configuration
  4. ls -ld /home/knime/knime-workspace

They should be owned by the same uid/gid the container runs with.

If the directories were copied in by root in the Dockerfile, or if the AP was unpacked by root, then you may need to assign ownership over to USER knime after it completes so that knime user can read/write the files and directories when it runs.

Regards,
Nickolaus

1 Like
3

thanks a lot, but I am using the workflow published from the hub.knime.com, and I ran it as the admin., and nothing changed. I didn’t go into the CLI and make any changes. Just wonder if anyone has ran that workflow (v2) and successfully built a 5.10 EC? thank again in advance.