You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Artifactory running inside a container on a Windows machine users can't restart artifactory due to issues with mounted storage. As workaround excluded security folder from the list of volumes inside docker compose file.
The error is the following:
[art-init] [ERROR] (o.a.w.s.ArtifactoryContextConfigListener:94) - Application could not be initialized: The folder containing the key file /opt/jfrog/artifactory/etc/security/access/keys has too broad permissions!
Please limit access to the Artifactory user only!
There is a JIRA for this as well, as the documentation examples also lead to the same problem.
It may be a good idea to at least just mention it on the documentation.
The text was updated successfully, but these errors were encountered:
When using Artifactory running inside a container on a Windows machine users can't restart artifactory due to issues with mounted storage. As workaround excluded security folder from the list of volumes inside docker compose file.
The error is the following:
[art-init] [ERROR] (o.a.w.s.ArtifactoryContextConfigListener:94) - Application could not be initialized: The folder containing the key file /opt/jfrog/artifactory/etc/security/access/keys has too broad permissions!
Please limit access to the Artifactory user only!
There is a JIRA for this as well, as the documentation examples also lead to the same problem.
It may be a good idea to at least just mention it on the documentation.
The text was updated successfully, but these errors were encountered: