Closed ajcontrib closed 10 months ago
@ajcontrib : I could see you are using an old version of chart and the application version is soon to reach EOL. Can you try to use the latest version of the chart and let us know if the issue persist.
@shahiinn thanks for the hint, it has actually disapeared with the latest helm chart version but a new one with the same nature has appeared:
/opt/jfrog/router/app/bin/entrypoint-router.sh: line 111: /opt/jfrog/router/app/router/router.pid: Read-only file system
Hi @ajcontrib, Are you running into an issue or it's just an observation?
Hi @oumkale yes we are running into an issue using the latest helm chart version of artifactory
Please can you share logs and values.yaml ?
resolved by adding an emptyDir volume and an init-container that copies the original content of the tomcat directory into that volume and mount it back in the main container artifactory
Artifactory installed from official helm chart is not running due to a unwritable directory issue
Is this a request for help?: Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Version of Helm and Kubernetes: 107.35.2
Which chart: artifactory
Which product license (Enterprise/Pro/oss):
JFrog support reference (if already raised with support team):
What happened: Artifactory is not running on kubernetes
What you expected to happen: Artifactory UP and running.
How to reproduce it (as minimally and precisely as possible): install helm chart with mentioned version and default values.
Anything else we need to know: Our kubernetes clusters prevent apps from writing on filesystem