{"push_id":745837696,"size":4,"distinct_size":4,"ref":"refs/heads/fedora-1.8","head":"ba026e34ffbe835e48ce9e07c40cf413c62404cf","before":"7c970091951bda5e03a71936fe1ebf6861f1627e","commits":[{"sha":"b31f8ed2c570f864ad9a0673d4cad85d672c7088","author":{"email":"ea3139ea422390c9a8bd6d7fb9ba423400fabbd1@redhat.com","name":"Michal Minar"},"message":"Add --add-registry and --block-registry options to docker daemon\n\nThe first option allows to prepend additional registries to a public\none. These will be queried one after another - in the same order they\nwere given - when pulling images.\n\nFor example:\n\n    --add-registry=foo.com\n    --add-registry=bar.com\n\nWould cause a\n\n    docker pull myapp\n\nto search\n\n    foo.com/myapp\n    bar.com/myapp\n    docker.io/myapp\n\nThe second option builds a list of banned registries. Docker daemon will\nprevent user from any communication with such registries. This option\nrecognizes a special keyword \"public\" denoting public Docker registry.\n\nSo for example adding `--block-registry=public` to daemon flags of\nprevious example would result in searching the same registries except\nfor `docker.io/myapp`.\n\nBoth flags are marked as experimental in man pages.\n\nThis would allow companies and vendors to specify registries which\ncontain content that the companies will not allowed to be stored at\ndocker.io.\n\nThe same applies to `FROM` statement in Dockerfile when issuing a build.\n\nThis patch also causes all pulled repositories to be fully qualified -\nincluding those coming from the public registry.\n\nDocker-DCO-1.1-Signed-off-by: Dan Walsh <dwalsh@redhat.com> (github: rhatdan)\nSigned-off-by: Michal Minar <miminar@redhat.com>","distinct":true,"url":"https://api.github.com/repos/rhatdan/docker/commits/b31f8ed2c570f864ad9a0673d4cad85d672c7088"},{"sha":"255b3cb18641d6e26a49d3376a868dc14aa74e09","author":{"email":"ea3139ea422390c9a8bd6d7fb9ba423400fabbd1@redhat.com","name":"Michal Minar"},"message":"Improved searching experience\n\n- Prepend indicies to search results.\n- Prefix remote name with registry name.\n- Shorten index name if it's not an ip address.\n- Added `--no-index` option to avoid listing the index name.\n- Changed sorting of entries when index is preserved:\n\n  1. sort by `index_name`\n  2. sort by `star_count`\n  3. sort by `registry_name`\n  4. sort by `name`\n  5. sort by `description`\n\n- Changed sorting of entries when index is omitted:\n\n  1. sort by `registry_name`\n  2. sort by `star_count`\n  3. sort by `name`\n  4. sort by `description`\n\nExample (with just first two columns left):\n\n    $ sudo docker search mongo\n    INDEX       NAME                                                     DESCRIPTION\n    docker.io   docker.io/mongo                                          MongoDB docu...\n    [...]\n    myregistry  docker.io/mongo                                          test\n    [...]\n    redhat.com  docker-registry.usersys.redhat.com/goldmann/eap-mongodb\n    [...]\n\nDocker-DCO-1.1-Signed-off-by: Daniel Riek <riek@redhat.com>\nSigned-off-by: Michal Minar <miminar@redhat.com>","distinct":true,"url":"https://api.github.com/repos/rhatdan/docker/commits/255b3cb18641d6e26a49d3376a868dc14aa74e09"},{"sha":"32b455ce9e02b7f2fddfb59b99141cd8133bfce3","author":{"email":"ea3139ea422390c9a8bd6d7fb9ba423400fabbd1@redhat.com","name":"Michal Minar"},"message":"Fixed docker's authentication issue\n\nDocker client sends configuration file with stored credentials together\nwith several requests to Docker daemon. Daemon then takes the first\nauthentication information and tries to use it against any registry it\ncontacts. This results in authentication errors while trying pull from\nany registry but the one stored first in configuration file. This patch\nchecks, whether the given credentials belong to desired endpoint before\ncreating an new session.\n\nThis is just a workaround. Robust solution would be to iterate over all\navailable authentication data and choose the right ones for registry\ncurrently processed. And client would have to pass all possibly needed\ncredentials to docker daemon with any request (it does so only in rare\ncases like docker build).\n\nSigned-off-by: Michal Minar <miminar@redhat.com>","distinct":true,"url":"https://api.github.com/repos/rhatdan/docker/commits/32b455ce9e02b7f2fddfb59b99141cd8133bfce3"},{"sha":"ba026e34ffbe835e48ce9e07c40cf413c62404cf","author":{"email":"ea3139ea422390c9a8bd6d7fb9ba423400fabbd1@redhat.com","name":"Michal Minar"},"message":"Allow for remote repository inspection\n\n**Inspect remote images**\n\nExtended server API to allow for inspection of remote images. If a short\nname is given, list of additional registries will be queried until a\nrepository is found. This allows for remote inspection without\ndownloading image layers.\n\nThe URL is following:\n\n    /<apiVersion>/images/<repoName>/json?remote=1\n\nThe output is the same json as for local images. However, it excludes\nfew attributes specific only to local images:\n\n- GraphDriver\n- VirtualSize\n\nAnd it adds some additional attributes:\n\n- Digest\n- Tag\n- Registry\n\n**List tags of remote repository**\n\nExtended server API to allow for listing of remote repositories.\n\nThe URL is following:\n\n    /<apiVersion>/images/<repoName>/tags?remote=1\n\nIf a short name is given, list of additional registries will be queried\nuntil a repository is found.\n\nReturned is a json in following format:\n\n    { \"Name\"    : \"<repoName>\"\n    , \"TagList\" : [ {\"<tag1>\" : \"<ID1>\", \"<tag2>\" : <ID2>\" } ]\n    }\n\nQuirks and TODOs:\n - By default V1 registry enpoints are queried because they provide tags\n   with associated image IDs. If not available, V2 endpoint will be\n   tried. In such a case the output will lack image IDs though.\n\nSigned-off-by: Michal Minar <miminar@redhat.com>","distinct":true,"url":"https://api.github.com/repos/rhatdan/docker/commits/ba026e34ffbe835e48ce9e07c40cf413c62404cf"}]}