Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

BUG: Missing security context for master and slave when using persistence mode. #41

Open
hetii opened this issue Mar 16, 2020 · 1 comment

Comments

@hetii
Copy link

hetii commented Mar 16, 2020

H.
When using persistent storage artemis is not able to write to his data path and raise:

AMQ222141: Node Manager can not open file /var/lib/artemis/data/journal/server.lock: java.io.IOException: No such file or directory

This is due the fact that in current helm chart artemis use own user called "artemis" who don't have proper permission to write on requested PVC.

To solve this issue I add a securityContext to both
activemq-artemis/templates/master-statefulset.yaml
and
activemq-artemis/templates/slave-statefulset.yaml

  securityContext:
    fsGroup: 1000
    runAsUser: 1000
    runAsNonRoot: true

This solve the issue and master and slave is able to write his stuff to given PVC.

@bessalahAmar
Copy link

thanks , worked for me too ;

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants