/rawhide container worked was January 25.
It's been reported as
https://bugzilla.redhat.com/show_bug.cgi?id=2165004.
--
Jan Pazdziora | Sr. Principal Software Engineer | Red Hat
___
cloud mailing list -- cloud@lists.fedoraproject.org
T
Hello,
it seems registry.fedoraproject.org/fedora:25 was recently updated to
some 10 month old version f3535ce68198 where packages cannot be
installed due to missing
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64:
https://bugzilla.redhat.com/show_bug.cgi?id=1460094
--
Jan Pazdziora
On Tue, May 23, 2017 at 11:27:13AM -0500, Adam Miller wrote:
> On Tue, May 23, 2017 at 9:38 AM, Jan Pazdziora wrote:
> >
> > The bugzilla was addressed -- can we give
> >
> > registry.fedoraproject.org/fedora:26
> >
> > another try?
>
> Yes
ressed -- can we give
registry.fedoraproject.org/fedora:26
another try?
--
Jan Pazdziora
Senior Principal Software Engineer, Identity Management Engineering, Red Hat
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
On Thu, May 11, 2017 at 10:04:19AM -0500, Dennis Gilmore wrote:
> El mié, 10-05-2017 a las 22:47 -0500, Adam Miller escribió:
> > On Tue, May 9, 2017 at 7:22 AM, Jan Pazdziora
> > wrote:
> > >
> > > One problem with the current Fedora 26 image is that it enables
On Mon, May 08, 2017 at 01:59:36PM -0500, Adam Miller wrote:
> On Thu, May 4, 2017 at 6:55 AM, Jan Pazdziora wrote:
> > On Thu, Apr 20, 2017 at 10:39:22PM -0500, Adam Miller wrote:
> >> Hello all,
> >> On behalf of the Fedora Atomic WG[0] and Fedora Release
> &
and
if we do not want to encourage the use of
RUN dnf upgrade -y
in every Dockerfile, we might want to make it easy for people to
consume fresh content.
Incidently, registry.fedoraproject.org/fedora:25 is rather new, just
13 days old.
--
Jan Pazdziora
Senior Principal Software E
On Fri, Apr 28, 2017 at 09:03:48AM -0500, Adam Miller wrote:
> On Fri, Apr 28, 2017 at 2:39 AM, Jan Pazdziora wrote:
> >
> > If we are building building images
> >
> > FROM fedora:25
> >
> > should we start using
> >
> > FROM regi
wer Fedora 25 image than
registry.fedoraproject.org/fedora. Is that expected?
If we are building building images
FROM fedora:25
should we start using
FROM registry.fedoraproject.org/fedora:25
instead in Dockerfiles? If merely fedora does not point to whatever
is the authoritat
adelton added a new comment to an issue you are following:
``
> BTW Even if we got oci-systemd-hook into debian, we would still need to get
> projectatomic/docker in since docker rejected the patch to run hooks directly.
Would it help if the execution of the hook was dependent on some label in t
et Alpha even after Beta is out might be
useful. I'd propose to remove all pre-release tags one month after the
GA (fedora:25 in this example) has been made available.
--
Jan Pazdziora
Senior Principal Software Engineer, Identity Management Engineering, Red Hat
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
"net:[4026531957]" dev="nsfs"
> ino=4026531957 scontext=system_u:system_r:iptables_t:s0
> tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0
It's already present on Fedora 22:
https://bugzilla.redhat.com/show_bug.cgi?id=1266391
--
Jan Pazdzi
eded in other places (possibly patching docker with
something like https://github.com/docker/docker/pull/9239) to minimize
the impact.
--
Jan Pazdziora
Principal Software Engineer, Identity Management Engineering, Red Hat
___
cloud mailing list
cloud@lis
good approach, but requires updating both containers
> and hosts with kdbus.
We need Fedora 22 to continue supporting existing images.
Can I assume that the note about Docker in that change page makes it
an effective blocker or is it necessary to raise the issue some more?
--
Jan Pazdziora
Pri
infrastructure (I know it's not 3-DES anymore, but still)?
The passwords seem to be reset in /etc/rc.local by an random string.
I was surprised to see the passwords change upon every reboot but
it the found the cause and thought that maybe the AMI authors had good
reason to set it up this
376.html
http://lists.fedoraproject.org/pipermail/cloud/2010-November/000398.html
https://bugzilla.redhat.com/show_bug.cgi?id=651861
?
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
___
cloud mailing list
cloud@li
;0's are replaced with account-specific numbers and things.
>
> At the moment you need all six of these variables, though the *_KEY
> variables may not be necessary in future releases.
Ahh. I don't have the EC2_(ACCESS|SECRET)_KEY's, I just use the
cer
EC2_SECRET_KEY, EC2_CERT, EC2_PRIVATE_KEY, S3_URL, EUCALYPTUS_CERT by
default.
Is there anything else I need to have setup beyond EC2_CERT and
EC2_PRIVATE_KEY?
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
__
On Wed, Nov 03, 2010 at 04:16:56PM +0100, Marek Goldmann wrote:
>
> Attach EBS volume, say on /dev/sdf and it'll be available in instance under
> /dev/xvdf.
>
Great, thanks.
--
Jan Pazdziora
Principal Software Engineer, Satellite Eng
to life.
Any suggestion about the device attaching (or about the conversion to
EBS in general)?
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
; Awesome! That does the trick. Thanks, Justin.
Confirming. Thanks.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
On Wed, Nov 03, 2010 at 10:10:48AM +0100, Jan Pazdziora wrote:
> On Wed, Nov 03, 2010 at 12:30:43AM -0400, Jon Masters wrote:
> > >
> > > Looking forward to giving the AMIs a spin :)
> >
> > I checked the Fedora Project website (which is lacking a giant s
52b
instance-store paravirtual
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
23 matches
Mail list logo