#97 Maintaining Fedora docker images for f22
Closed None Opened 4 years ago by jzb.

f22 docker alpha images were not tested or really looked after afaict. According to dgilmore we have pulled in server pkgs instead of cloud, and have cockpit packages coming into the container. That's bad. We need to see who "owns" testing of the base images.


Decided in today's meeting - I'll get with the base working group to see about handling testing and promotion of this image as part of Cloud edition.

Will you post something on the mailing list when there's something I can test? I'm eager to get a bunch of images I've built on track for F22.

Replying to [comment:1 jzb]:

Decided in today's meeting - I'll get with the base working group to see about handling testing and promotion of this image as part of Cloud edition.

Any progress working with base WG?

FWIW I have a test case / scenario working with the Beta TC 2 tarball! https://bitbucket.org/znmeb/osjourno/src/113da73c63f58b1226fa78bb58c5636563983757/4Experimental/osjourno-sports/?at=master

So far it looks like everything I'm now building on the F21 Docker image base will port easily to F22 with comparable image sizes.

Update:

1) The current state of the Docker image (TC8 beta) is non-worrying at least according to the minimal testing I've done so far.

2) Have asked the Web team about the current state of the Docker image as a spin. It's sort of hidden on the spins page (see: https://fedorahosted.org/fedora-websites/ticket/317#comment:5)

3) Have raised the discussion on -devel about moving Docker image to Cloud for promotional purposes. Have not yet raised a discussion about testing. https://lists.fedoraproject.org/pipermail/devel/2015-April/209742.html

Following up on this - It looks like we're not going to move the Docker image for F22, but we should re-visit placement and "ownership" of the image for F23. We should probably have the cloud team responsible for care and feeding but we need to reduce churn here...

Login to comment on this ticket.

Metadata