On Wed, Mar 2, 2016 at 12:52 PM, Vaclav Pavlin <vpavlin at redhat.com> wrote: > > > On Tue, Mar 1, 2016 at 5:26 PM, Mohammed Zeeshan < > mohammed.zee1000 at gmail.com> wrote: > >> This is how you sync a registry >> >> pulp-admin docker repo create --repo-id=synctest --feed=https://index.docker.io --upstream-name=busybox >> >> In other words the sync happens for a single specific repository/image at > the time. Then the delivery step might call this to publish the results, > right? > I believe busybox is the repo name here to indicate the image. we also need a way to track based on image name with tags. Once we sync based on the image with tags, we will be able to trigger build stages. Regards Bamacharan > >> On Tue, Mar 1, 2016 at 9:53 PM, Vaclav Pavlin <vpavlin at redhat.com> wrote: >> >>> Hey, >>> >>> we already have that registry - it's part of the OpenShift, right?:) Can >>> we sync only specific namespaces/images/tags? >>> >>> Vašek >>> >>> On Tue, Mar 1, 2016 at 5:22 PM, Mohammed Zeeshan < >>> mohammed.zee1000 at gmail.com> wrote: >>> >>>> Hi >>>> >>>> We need to push to a docker registry, either docker hub or docker >>>> private registry and then sync the pulp/crane registry with that. >>>> The syncs pulls the metadata as well allowing docker pull to work with >>>> it. >>>> >>>> On Tue, Mar 1, 2016 at 9:43 PM, Karanbir Singh <mail-lists at karan.org> >>>> wrote: >>>> >>>>> On 01/03/16 16:04, Mohammed Zeeshan wrote: >>>>> > Hi, >>>>> > >>>>> > I just got off a half hour discussion with the pulp guys for the >>>>> > CentOS Container Pipeline registry story. >>>>> > >>>>> > 1. docker save x.tar produces a v1 tarball and not a v2 tarball >>>>> > 2. This tarball doesnt contain metadata such as tags and so on. >>>>> > 3. docker pull from docker 1.6 assumes the registry being pulled >>>>> from >>>>> > is a v2 registry >>>>> > 4. v1 registry has been depricated. >>>>> > 5. Currently, the only way to get a v2 repo into pulp or any other >>>>> > registry is to first push it to docker registry and then sync our >>>>> > registry to it. >>>>> >>>>> we already do this, since the builder uses its own local registry >>>>> >>>>> what does 'sync to our registry' involve ? >>>>> >>>>> >>>>> -- >>>>> Karanbir Singh >>>>> +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh >>>>> GnuPG Key : http://www.karan.org/publickey.asc >>>>> _______________________________________________ >>>>> CentOS-devel mailing list >>>>> CentOS-devel at centos.org >>>>> https://lists.centos.org/mailman/listinfo/centos-devel >>>>> >>>> >>>> >>>> >>>> -- >>>> *Mohammed Zeeshan Ahmed, * >>>> B.E Computer Science Engineering >>>> Certified IT & Cloud Architect & RHCSA >>>> +919986458839 >>>> Bengaluru, India >>>> >>>> https://mohammedzee1000.wordpress.com/ >>>> <http://mohammed-zeeshan.strikingly.com> >>>> >>>> _______________________________________________ >>>> CentOS-devel mailing list >>>> CentOS-devel at centos.org >>>> https://lists.centos.org/mailman/listinfo/centos-devel >>>> >>>> >>> >>> >>> -- >>> Developer Experience Team >>> Brno, Czech Republic >>> Phone: +420 739 666 824 >>> >>> >>> >>> _______________________________________________ >>> CentOS-devel mailing list >>> CentOS-devel at centos.org >>> https://lists.centos.org/mailman/listinfo/centos-devel >>> >>> >> >> >> -- >> *Mohammed Zeeshan Ahmed, * >> B.E Computer Science Engineering >> Certified IT & Cloud Architect & RHCSA >> +919986458839 >> Bengaluru, India >> >> https://mohammedzee1000.wordpress.com/ >> <http://mohammed-zeeshan.strikingly.com> >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel at centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel >> >> > > > -- > Developer Experience Team > Brno, Czech Republic > Phone: +420 739 666 824 > > > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > > -- Bamacharan Kundu IRC Nick- bamachrn http://bamacharankundu.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20160302/6f7e9ceb/attachment-0008.html>