Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-13928

Artifactory run with local directory volume in Docker for Windows fails to initialize due to directory permissions


    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.1.3
    • Fix Version/s: None
    • Component/s: Docker
    • Labels:
    • Environment:

      Docker for Windows


      docker run -d --name jfrog-artifactory-oss-latest -p 8081:8081 -v C:/path/to/data:/var/opt/jfrog/artifactory docker.bintray.io/jfrog/artifactory-oss:latest

      This produced an error at startup.

      2017-03-17 19:46:41,601 [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!

      Creating a named volume and having Artifactory mount against the file system in the MobyLinux VM that Docker for Windows provides worked since it was able to create the specific permissions Artifactory is evidently checking for. I don't know if there's a way on Windows to configure the data directory in a way that would cause whatever check Artifactory is doing to succeed. (I tried to download the OSS source bundle and figure out where this was and had no luck whatsoever...the documentation for this appears to be out of date or incomplete.)

      It's not a major issue, but it should be noted as a risk for people who want to experiment with Artifactory on Windows. This is super easy to do with Docker, but folks who decide to try to mount the data externally (whether for learning what's there or just having an easy way to back it up) will be blocked. I wanted to make sure you were aware of the limitation.




            • Assignee:
              nlwillia Nathan Williams
            • Votes:
              2 Vote for this issue
              5 Start watching this issue


              • Created: