Vasku, I like the idea and the workflow. If I understand the workflow right - the layered
image will build on top of base image picked in COPR (eg. Fedora20 or CentOS7)? Also would
it make sense to run our own docker registry and have in connected to docker.io?
----- Original Message -----
Could you please have a look at attached diagram briefly describing
potential architecture of the image building service? Would this be a
On 24.7.2014 10:42, Václav Pavlín wrote:
> On St 23. červenec 2014, 13:33:06 CEST, Richard Marko wrote:
>> On 07/23/2014 10:44 AM, Nick Coghlan wrote:
>>> On 07/23/2014 01:42 AM, Václav Pavlín wrote:
>>>> What do you think? Do you think this makes sense for copr?
>>> If we could use COPR to make Beaker packages for Fedora and EPEL *and*
>>> upload Dockerfiles to generate Docker images for the various
>>> that would be seriously cool. On the other hand, it might make more
>>> sense as a separate service that reacts to fedmsg events indicating new
>>> COPR builds are available.
>> +1 for separate service.
> I am not against separate service. The separate service would probably
> simply mean running Docker in some cloud instance and call it's API
> through docker-python bindings and then collect the results.
> Lead Infrastructure Engineer
> Developer Experience
> Brno, Czech Republic
Lead Infrastructure Engineer
Brno, Czech Republic
copr-devel mailing list