We have a repository on Github named Fedora-Dockerfiles . The Repository
contains Dockerfiles but those are not **atomic** specific.
So adding ability to use **atomic** command will make **other hosts** lose
the ability to use the Dockerfiles.
Since we are focusing on having production ready Dockerfiles for Atomic
host, Should we create a separate repository that contains Atomic specific
Hi folks, due to travel and various obstacles, we're not able to host a recorded demo this month. Instead we've put together a status report that includes some additional highlights we think you might be interested in. If you have feedback and/or think this works well, I'd love to know b/c I think this vehicle covers more information than a demo alone so I might do both in the future if it's worth it.
Apologies for missing the actual show and tell - if there's anything you'd like to see specifically, I'm sure we can arrange something.
I was recently discussing some items around docker layered image
release process in the future with Randy (bowlofeggs) and Patrick
(puiterwijk). As a side effect of our discussion there were two
questions I wanted to ask of the Cloud WG:
1) Do we want to maintain docker images for every Fedora Release or do
we want to focus only on latest? (i.e. - do we want to maintain them
like we do rpms or take a different position)
2) Do we want to keep around multiple versions of a container?
If we had the following images:
One we release to stable 0.95-1.25, can we delete -1.24 and/or
-1.23? What kind of retention do we want here? (Note that rpm content
does not currently maintain a N and N-1 in the repositories)
On thursday night the image builds didn't run because pagure was intermittently down.
For the past 2 nights they have failed to build. I'm not sure why exactly but there is
some libvirt error  in the logs.
Dennis has been looking into this for us.
I'm hoping we can an image built to look at before the freeze on Tuesday. If we do get
one I'll post here and ask everyone to give it a spin if they can.
Today, and tomorrow are holidays in India. On Wednesday I will be
travelling to Cambodia for FUDCon APAC. I will be back home on Monday
evening. I am hoping to have a working internet connection during the
Fedora Cloud Engineer
CPython Core Developer
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2016-11-02 from 17:00:00 to 18:00:00 UTC
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
walters added a new comment to an issue you are following:
To repeat again, I am a big fan of this effort - having a nicer interactive experience is great! The cockpit guys were working on something similar to what CoreOS does with displaying the host IP addresses in the console too.
But the PAM and update stacks are about some of the most senstitive/critical aspects of the OS, and we have to be really careful when tying them together.
To reply, visit the link below or just reply to this email