-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot write to /opt/jfrog/router/app/router/router.pid: Permission denied #1857
Comments
@oniabifo Thanks for reaching out ! we need more details to reproduce . Can you share below information ?
|
Hello @chukka Thanks for reaching out kubernestes flavour and version helm command used
complete console logs
|
@oniabifo can you let us know the license that you are using |
@chukka I am using the 30 days free trial from the jfrog website for this |
@oniabifo I tried with below commands , it works with out any issues , can you try again with latest version
|
@chukka still failing. Also noticed nginx isn't starting up
|
@oniabifo can you confirm if you are using latest version of chart Can you provide me output of this command |
@chukka it returned nothing. I also have another question, i pulled this image
Could there be a reason why? it seems it is running updateConf.sh in the background and there might be something going on in that file |
Closing, If additional support is required please let us know. |
Has this been closed as a resolution has been provided? Could you clarify as I am getting a similar error while trying to install xRay? |
The issue closed without resolution as our team wasn't able to reproduce the issue with the information provided. |
Hitting this error as well, I have a cluster with kubeadm, k8s version v1.29.3. Closing it without a resolution doesn't make sense @gitta-jfrog . This is the error I'm getting from the router container:
Im getting similar issues with the other containers 'permission denied'. I think there is some setup we need to do for the PV. This helm chart expects a pv to exists before it can claim it with pvc. My pv setup is with nfs. Here is my setup:
|
Thank you for raising these concerns. However, we were unable to reproduce them, and it seems the issue stems from Docker on the host. Could you please take a look into below ref and let us know if you need any help? Reference issue: docker-library/golang#467 |
If you are having support as part of your subscription - please open support ticket and our support engineers will work with you up to full resolution. if you are not having support - I'll ask you to open a new Github issue with all the details (version before, version after upgrade, database type and values yaml) and I'll try to assist as much as I can. Upgrade to newer version (Artifactory 7.68 is already released one year ago is highly recommended, and will make easier for us to provide support) Thanks |
Artifactory installed from official helm chart is not running due to a permission denied 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.77.3
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
The text was updated successfully, but these errors were encountered: