[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-buildservice
Subject:    New feature: download on demand for container registries
From:       Michael Schroeder <mls () suse ! de>
Date:       2021-06-01 14:46:38
Message-ID: 20210601144638.GA5610 () suse ! de
[Download RAW message or body]


Hi buildservice enthusiasts,

we implemented a new feature in the build service: it is
not possible to configure container registries as
download on demand repositories. We already did that
in out instance for two registries:

registry.suse.com:
    available as project "SUSE:Registry" repository "standard"

registry-1.docker.io (the official docker registry): 
    available as project "Docker:Registry" repository "standard"

To make use of them, you need to add a corresponding
entry to your project path entry. (Do not make this the last
entry, as this entry is "path expanded" and provides the
packages of the base system. It's probably best to always
put it first.)

If OBS sees such a download on demand registry in the path,
it will collect all of the needed container references and
transmit them to the download on demand update daemon.
This daemon will then periodically check if a new version
is available, just like with a normal download on demand
repository.

This approach currently two limitations you should know:

1) Only the scheduler does this collection. This means
   that not yet requested containers will not work in
   "osc build".

2) Collecting currently does not work for remote OBS
   instances, e.g. you cannot get not yet requested
   containers in IBS via the OBS interconnect.

(Both limitations may get lifted in the future.)

Enjoy,
  Michael.

-- 
Michael Schroeder          SUSE Software Solutions Germany GmbH
mls@suse.de      GF: Felix Imendoerffer HRB 36809, AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
[prev in list] [next in list] [prev in thread] [next in thread]