:: Re: [devuan-dev] Future of my "padd…
Startseite
Nachricht löschen
Nachricht beantworten
Autor: Boian Bonev
Datum:  
To: devuan developers internal list
Betreff: Re: [devuan-dev] Future of my "paddy-hack" Devuan Docker images
Hi Olaf,

In the meantime Docker hub approved Devuan for the Docker-Sponsored
Open Source program.

I will forward the confirmation email to you in a private email (with
some more of my contact info).

I have selected "devuan" in the registration, but didn't create that
initially, it seems that Docker hub will create it and somehow we will
gain access, that will be shared with you.

With best regards,
b.

On Sat, 2022-10-15 at 18:07 +0900, Olaf Meeuwissen wrote:
> Hi Jaromil,
>
> Jaromil <jaromil@???> writes:
>
> > dear Olaf,
> >
> > many thanks for your message! as you know I'm making great use of
> > your
> > base images for what is being built here (6.6k pulls!)
> > https://hub.docker.com/r/dyne/devuan a docker image repo processed
> > and
> > pushed by our own Jenkins infra at Dyne.org rather than using the
> > docker
> > hub PaaS.
>
> Sorry for breaking the dyne/devuan builds for a while.  That was
> really
> due to GitLab.com not understanding "most recent" the way I did when
> cleaning up the registry.  I've patched up the mess and submitted an
> issue to get GitLab's container registry cleanup policy
> implementation
> fixed.
>
>   https://gitlab.com/gitlab-org/gitlab/-/issues/377417
>
> > Also the docker hub I'm publishing this is a "non-official" user
> > account
> > rather than an organization registered as open-source, something
> > I've
> > tried to do in the past with folks at Docker.com with no success
> > due to
> > their availability following the process... I mention this just to
> > say
> > that yes, there can be improvements, but hey all our time is
> > limited.
>
> I've got a Docker ID and will look at getting Devuan registered as an
> organization.
>
> > All considered I suggest we keep things as they are and either keep
> > using your current gitlab account paying 60$ per year with Devuan's
> > budget.
>
> It's actually 60US$/10GiB/year, so at 30GiB and counting, that would
> start out at 180US$/year.  As those 30GiB include a lot of historical
> images, I've been using timestamp tags so everything is kept, there
> is
> something to say for a policy of what should be kept.  If only to
> keep
> storage requirements in check.  I see that you only keep dyne/devuan
> images for each codename so you've got six tags.  My registry had
> 210+
> tags each for devuan, devuan/slim and devuan/builder.  Only that last
> one shared images layer with devuan/slim.
>
> > If you really like to move out of gitlab then I would have no
> > problem
> > updating the docker base images to point at your local repo.
>
> See my other post in the thread.  I'll be redoing the whole thing on
> Devuan's Gitea and will try to push images to one or more of the BIG
> container registries.
>
> > In an ideal world I guess we would integrating your scripts into
> > Devuan's gitea, but for that we'll need help from other volunteers
> > that know better than me what it entails.
>
> Guess I just became that volunteer ;-)
> --
> Olaf Meeuwissen
> _______________________________________________
> devuan-dev internal mailing list
> devuan-dev@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev