That is indeed a problem with the Docker V1 layout. The good news are that Docker V2 (available from Artifactory 3.7.0) no longer have this problem and manifests are now self contained without a global ".images" shared blobs folder. If all of your clients uses Docker 1.6 and above, you could migrate <http://www.jfrog.com/confluence/display/RTF/Docker+Repositories#DockerRepositories-MigratingaV1repositorytoV2> your repositories into a V2 layout and as you can see here <http://www.jfrog.com/confluence/display/RTF/Docker+Repositories#DockerRepositories-DockerRepositoryLayout> you can now give permissions on 3 different levels (the entire repository, the docker repository or for a specific tag).
I hope that helps. Regards, Shay On Fri, May 29, 2015 at 4:13 PM, priitliivak <[email protected]> wrote: > I have encountered exactly the same issue and no RewriteRule magic seems to > help here. Did you file a ticket or found any solution to this? > > Set of symbols allowed in repository name is very limited and Docker also > translates @ sign to tag name separator. Otherwise Apache could be > configured in a way to translate urls containing Artifactory repository > keys > as well. Something like > artifactory.smth.com:8443/namespace/repoName@docker-local > > > > -- > View this message in context: > http://forums.jfrog.org/Permissions-on-Docker-repositories-tp7580234p7580319.html > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users >
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
