I'm +1 for this, automation is very important in containers work.

+1

As for the ad-hoc release, few changes are blocked on the new s2i-core image on our side, that has been in candidate registry for few weeks now and we'd like to see it in official registry.. So, it would help us a lot if this image (and others from candidate) are pushed to proper repo soon..

I'd like to see "docker" and "cri-o" to be pushed to registry.fedoraproject.org/f27

Automation of releasing child container images is not completed in prod, @puiterwijk is working on it. Once thats done, we can be able release child container images.

@mohanboddu - any ETA on that work?

While we wait is it possible to manually release select images (in this case s2i-core, docker, and cri-o)?. I know manually doing things is not ideal, but it did allow us to ship things in the past (thanks @maxamillion)

I really need all the kubernetes- images pushed asap, there's been a bug in them waiting for release for some time now: https://github.com/projectatomic/atomic-system-containers/issues/156

:thumbsup:

Related:
- https://github.com/projectatomic/atomic-system-containers/issues/155
- https://github.com/projectatomic/atomic-system-containers/issues/43

FYI This is being discussed and looked at in IRC by @maxamillion and @mohanboddu.

From IRC:

14:42:25    dustymabe | do you have any idea when that might make it to prod? https://pagure.io/releng/issue/7217#comment-485157
14:43:19   puiterwijk | I am going to say by end of tomorrow is feasible.
14:43:37    dustymabe | so possible container relese tomorrow? do you mind updating the ticket with that info?

From IRC:
14:42:25 dustymabe | do you have any idea when that might make it to prod? https://pagure.io/releng/issue/7217#comment-485157
14:43:19 puiterwijk | I am going to say by end of tomorrow is feasible.
14:43:37 dustymabe | so possible container relese tomorrow? do you mind updating the ticket with that info?

@puiterwijk What was the outcome from the above conversation?

@puiterwijk What was the outcome from the above conversation?

He's going to try to have it by the end of the day today.

any update on this?

Any update on this now?

Is there any way I can help/support in this matter? I am a bit concerned that (at least) two "blocker type" bugs cannot be resolved bc. of a missing release automation.

• https://github.com/projectatomic/atomic-system-containers/issues/156
• https://github.com/projectatomic/atomic-system-containers/issues/155

@neufeind we're trying to pin down more help in IRC now as well.

This caused a delay. Speaking with @puiterwijk and @dustymabe this morning the belief is this should be fixed by Friday evening.

@smilner Where on IRC?

@neuhalje Freenode in #fedora-releng

update from patrick:

18:20:54      puiterwijk | dustymabe: okay, I think the FLIBS rebuild stuff is now setup in the infra. I'll be working with Rob/Mohan │ eroji
                         | to get a cycle running soon.                                                                               │ evilissimo
18:21:05      puiterwijk | However, I'm probably going to try to get it run tomorrow                                                  │ fabianvf
18:21:37      puiterwijk | (the reason being that I'd like to be there for the first time we run it in case it fails, and I'm going   │ fkautz
                         | to head out in 10 minutes) 

we hit some issues when running through the first build on friday. THose have been fixed and the builds are progressing, hopefully to be released today!

@dustymabe thanks for the update.

@dustymabe and @puiterwijk please keep us posted via this issue. Thanks!

TL;DR - your images should be in the registry and we'll do another release next week after the two week atomic release.

ok here is the latest update: all images have been rebuilt and pushed to the registry except s2i-base and ones that layer on top of it (there was some build error with them).

we didn't notice until later that the base images did not get pushed (so the base images are not new at this time, but the layered images are). We will do another FLIBS release next week including base images and will send a proper email.

Dusty, thanks for update!

This should fix the s2i-base failure: https://src.fedoraproject.org/container/s2i-base/c/cd22158f287f2bc5f5fed9cf6f40825fde3bfefc?branch=f27

Thanks dusty and tomas as well!

So, how is it gonna work now? My understanding of https://fedoraproject.org/wiki/Container:Guidelines is that the images will get built automatically and be pushed to stable registry every two weeks, right?

Further thinking... since docker is based on layering and it allows us to share some common parts for more containers, one thing I'm thinking on is how to build containers on updated base image -- e.g. the case with the s2i-base that Tomas mentions above -- if we change something in s2i-base image and depended containers use FROM registry.fedoraproject.org/f26/s2i-base:latest per guidelines, are we not able to build such depended containers within the two weeks? Or am I misunderstanding something?

Thanks dusty and tomas as well!

and thanks to @puiterwijk who mainly pushed this through the last mile

So, how is it gonna work now? My understanding of https://fedoraproject.org/wiki/Container:Guidelines is that the images will get built automatically and be pushed to stable registry every two weeks, right?

that is correct. My understanding is that even if they don't have new changes they will get rebuilt anyways on top of a newer base image (with possible security updates).

Further thinking... since docker is based on layering and it allows us to share some common parts for more containers, one thing I'm thinking on is how to build containers on updated base image -- e.g. the case with the s2i-base that Tomas mentions above -- if we change something in s2i-base image and depended containers use FROM registry.fedoraproject.org/f26/s2i-base:latest per guidelines, are we not able to build such depended containers within the two weeks? Or am I misunderstanding something?

The build process considers this and builds layered images after dependent layers have been built. If a new s2i-base container is built during a rebuild then new s2i-base-layer1 container would build on top of that s2i-base container that was just built.

Sooo, any updates here? I still don't see the automatic two-week-cadence push happening -- e.g. registry.fedoraproject.org/f26/s2i-core still not available, although built for looong time..

@mohanboddu , the blocking containers are now built for f27 see atomic #424.

Can run the release playbook.

Thanks
Clément

@cverna Okay, let me run that, thanks

Ok so I think we can close this ticket. :fireworks: .

Let's try to do another one in 2 weeks :)

thanks @cverna and @mohanboddu - closing ticket now!