# Weird manual workaround nedded for APM server and Maps server under ECK on OpenShift **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [May 15, 2025, 10:53am UTC](https://discuss.elastic.co/t/weird-manual-workaround-nedded-for-apm-server-and-maps-server-under-eck-on-openshift/378174 "2025-05-15T10:53:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![natharran](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@natharran](https://discuss.elastic.co/u/natharran)\ **Post date:** [May 15, 2025, 10:53am UTC](https://discuss.elastic.co/t/weird-manual-workaround-nedded-for-apm-server-and-maps-server-under-eck-on-openshift/378174/1 "2025-05-15T10:53:09Z")
Hello all, until recently I had Elastic stack running under ECK on OpenShift with no problems. However, after an upgrade to 9.0.0 (and now 9.0.1) APM server and Maps server stopped working, OpenShift emitting a weird error about executable not found in $PATH. So I did some manual digging in ECK-generated manifests and finally I went past the issues by modifying podTemplates for these resources like this: APM server: ```auto podTemplate: spec: containers: - name: apm-server env: - name: PATH value: "/bin:/usr/bin:/usr/share/apm-server" volumeMounts: - name: non-persistent mountPath: /usr/share/apm-server/data readOnly: false volumes: - name: non-persistent emptyDir: {} ``` When finally starting the container, there was another error about not being able to create the data directory, hence the emptyDir. Maps server: ```auto podTemplate: spec: containers: - name: maps command: - /bin/sh - -c - "cd /usr/src/app/server/app && node index.js" ``` So I've got it working. However, I hardly think this should be compulsory, or is it? I didn't find these issues documented anywhere. Is there a better way? Thank you. ---
**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\ **Post date:** [May 19, 2025, 8:29am UTC](https://discuss.elastic.co/t/weird-manual-workaround-nedded-for-apm-server-and-maps-server-under-eck-on-openshift/378174/2 "2025-05-19T08:29:50Z")
Hi, I can't reproduce the issue for the APM server. Could you share the original manifest and your OpenShift version? With regard to Maps I can confirm that the image does not start since `9.0.0`: ```auto Warning Failed 17m (x9 over 18m) kubelet Error: container create failed: open executable: Operation not permitted ``` I'll create a GitHub issue in the ECK repo and try to understand the root cause. ---
**Author:** ![natharran](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@natharran](https://discuss.elastic.co/u/natharran)\ **Post date:** [May 19, 2025, 10:11am UTC](https://discuss.elastic.co/t/weird-manual-workaround-nedded-for-apm-server-and-maps-server-under-eck-on-openshift/378174/3 "2025-05-19T10:11:14Z")
Hello Michael and thank you for your response. OpenShift version is 4.16.30 and I deployed APM server via [Elastic helm chart](https://github.com/elastic/cloud-on-k8s/tree/main/deploy/eck-stack/charts/eck-apm-server) with the following values.yaml before adding the podTemplate part: ```auto fullnameOverride: "apm-server-poc" version: 9.0.1 count: 1 config: monitoring: enabled: false cluster_uuid: ZJn6TF45SOuEHCkdPCgVcQ http: enabled: true port: 5066 host: 0.0.0.0 http: service: spec: ports: - name: http port: 8200 targetPort: 8200 - name: metrics port: 5066 targetPort: 5066 elasticsearchRef: name: elastic-poc kibanaRef: name: kibana-poc ``` Regarding the Maps server I got a different error from yours. It was the same error as with the APM server about binary not being found in $PATH. I also have APM and Maps server on another infrastructure where they run as containers as well (no k8s or OpenShift there, just Docker) and they work without problems. ---
**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\ **Post date:** [May 19, 2025, 11:26am UTC](https://discuss.elastic.co/t/weird-manual-workaround-nedded-for-apm-server-and-maps-server-under-eck-on-openshift/378174/4 "2025-05-19T11:26:09Z")
Interesting, I'm using `4.18.1`. For Maps the `node` binary is in `/usr/bin/node`, which is in the `PATH` variable: `PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"` This variable was not changed between `8.17` and `9.0.0`. So I don't understand why you would get an error about the binary not in `$PATH`. I created [ElasticMapsServer does not start on OpenShift since 9.0.0 · Issue #8655 · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/issues/8655) but I'm a bit stuck for now. ---
**Author:** ![natharran](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@natharran](https://discuss.elastic.co/u/natharran)\ **Post date:** [May 19, 2025, 2:44pm UTC](https://discuss.elastic.co/t/weird-manual-workaround-nedded-for-apm-server-and-maps-server-under-eck-on-openshift/378174/5 "2025-05-19T14:44:06Z")
Yes, the thing about `$PATH` is strange, because if I override the default container command with ```auto tail -f /dev/null ``` and I enter the container, the `$PATH` is as you describe it and these components (APM, Maps) can be started manually OK (though Maps only start if I'm in `/usr/src/app/server/app` where I need to `cd` first). I'm, however, not the OpenShift administrator and can't access its various settings so I don't know what can be the cause.