Hey all,
So - the good news is that we are tantalizingly close[1] to a good build
for the Atomic image. (We're missing the docker-storage-setup package,
and I think it's missing the config to pull in updates using atomic update.)
The bad news is that it's also tantalizingly close to Wednesday, wh
On Tue, Nov 11, 2014 at 07:10:08PM -0500, Matthew Miller wrote:
> See http://koji.fedoraproject.org/koji/taskinfo?taskID=8104289
> It looks basically good. Still missing docker storage setup, though.
> That package is built and pushed to stable, so I guess it's just
> missing from the json?)
Nope,
See http://koji.fedoraproject.org/koji/taskinfo?taskID=8104289
It looks basically good. Still missing docker storage setup, though.
That package is built and pushed to stable, so I guess it's just
missing from the json?)
--
Matthew Miller
Fedora Project Leader
__
#84: publicize fedora-dockerfiles
---+---
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Untested, but I think this will fix the Atomic compose.
CC'ing fedora-cloud as my patch also touches the invocations
for mainline cloud as well as the docker base image.
We need to specify --version to ensure the build host is
allowed to use kickstart syntax from the target version.
Remove the >
#84: publicize fedora-dockerfiles
---+---
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Hi,
On Mon, Nov 10, 2014, at 08:31 AM, Josh Boyer wrote:
> Er... that's a strange interpretation of how to not call something a
> system wide change. Even if you had someone doing the rel-eng work,
> it's still a system wide change. Particularly since it's going across
> several groups and comp
On Tue, Nov 11, 2014 at 1:10 PM, Lars Kellogg-Stedman wrote:
> On Tue, Nov 11, 2014 at 12:24:02PM -0500, Josh Boyer wrote:
>> If it doesn't look like that, then something is indeed odd.
>
> The output of "lsinitrd" does, indeed, look more sane...but now I am
> confused by the fact that running "dr
On Tue, Nov 11, 2014 at 12:24:02PM -0500, Josh Boyer wrote:
> If it doesn't look like that, then something is indeed odd.
The output of "lsinitrd" does, indeed, look more sane...but now I am
confused by the fact that running "dracut -f" does not seem to result
in the same thing (an initramfs image
On Tue, Nov 11, 2014 at 12:17 PM, Lars Kellogg-Stedman wrote:
> I just grabbed the F21 beta cloud image from:
>
>
> http://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Cloud/Images/x86_64/Fedora-Cloud-Base-20141029-21_Beta.x86_64.qcow2
>
> It looks like the initramfs on thi
I just grabbed the F21 beta cloud image from:
http://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Cloud/Images/x86_64/Fedora-Cloud-Base-20141029-21_Beta.x86_64.qcow2
It looks like the initramfs on this image is corrupt; it appears to be
an uncompressed CPIO archive with tr
On Mon, Nov 10, 2014 at 10:58:44PM -0600, Joe Brockmeier wrote:
> One thing I have noticed - we don't have a "place" for Fedora Docker
> images. Since they were taken on by the base WG, they have sort of been
> orphaned under products. Do they belong under Server? Cloud? Spins?
It'd be nice to hav
#84: publicize fedora-dockerfiles
---+---
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
#84: publicize fedora-dockerfiles
---+---
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (F
On 11/11/2014 12:15 AM, Dennis Gilmore wrote:
> the Tuesday and Thursday times should work okay when I am in the states.
Ah - when will that be?
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
j...@redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpres
15 matches
Mail list logo
