docker-storage-setup fails on F22 cloud image
by Dusty Mabe
docker-storage-setup fails on our cloud image because there is no storage for it
to configure. In my case I am just testing on openstack with no ephemeral disks
attached to the instance.
All you need to do to show this is install and start docker and then
you will see:
[root@f22 ~]# systemctl status docker-storage-setup
● docker-storage-setup.service - Docker Storage Setup
Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2015-08-05 14:15:14 UTC; 4min 3s ago
Process: 6951 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=3)
Main PID: 6951 (code=exited, status=3)
Aug 05 14:15:14 f22 docker-storage-setup[6951]: WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Aug 05 14:15:14 f22 docker-storage-setup[6951]: Metadata volume docker-poolmeta already exists. Not creating a new one.
Aug 05 14:15:14 f22 docker-storage-setup[6951]: /run/lvm/lvmetad.socket: connect failed: No such file or directory
Aug 05 14:15:14 f22 docker-storage-setup[6951]: WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Aug 05 14:15:14 f22 docker-storage-setup[6951]: Please provide a volume group name
Aug 05 14:15:14 f22 docker-storage-setup[6951]: Run `lvcreate --help' for more information.
Aug 05 14:15:14 f22 systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Aug 05 14:15:14 f22 systemd[1]: Failed to start Docker Storage Setup.
Aug 05 14:15:14 f22 systemd[1]: Unit docker-storage-setup.service entered failed state.
Aug 05 14:15:14 f22 systemd[1]: docker-storage-setup.service failed.
Should we fix this so that there isn't a failed unit if there is no storage to configure?
Dusty
8 years, 3 months
Rescheduling this weeks Blocker review meeting
by Mike Ruckman
Hey all,
It seems the lack of sleep from Flock caught up with me Sunday night and I didn't wake up in time
to run the blocker review scheduled for Monday morning. We currently have 6/7 proposed blockers
for Beta and Final, so I think it will still be good to have a Blocker review this week. Does
this Thursday (2015-08-20) at 16:00 UTC work for people? If there's a better time, please
respond to the test list and we can find a better window to run the review.
Thanks!
Mike Ruckman
8 years, 3 months
Cloud WG membership renewal
by Haïkel
Hi ladies and gentlemen,
The Cloud WG regularly renew membership, and this time, we have
two seats available.
So if you're interested and able to dedicate a significant amount of time
then you're more than welcome to apply.
Candidates preferably could reply to the mailing list but you can
email me directly
if you're more comfortable this way. Please state what are your interests and
what you'd like to let us know.
Nominations will be closed by August, 24 (12AM UTC), then, the current members
will choose the new ones.
I'd like to thank Andy Grimm (agrimm) and David Gay (oddshocks) for their
fantastic work within the WG.
Andy Grimm will still serve as our liaison to the operations team and
manage access
to our cloud accounts.
Regards,
H.
PS: WG membership is not mandatory to join the meetings and start working :)
8 years, 3 months
ecryptfs on F21 EC2 instance
by Ron Wagner
Greetings,
If this is the wrong list, kindly point me to the correct one.
I am trying to get ecryptfs running on a Fedora 21 EC2 instance on Amazon’s AWS service. Not having any luck whatsoever, I brought up a virtual F21 on my desktop computer in VMWare Fusion to test the procedure to get ecryptfs running, and was successful.
Some info about my EC2 instance:
AMI: Fedora-Cloud-Base-20141203-21.x86_64-us-east-1-0
Kernel ID: aki-919dcaf8, Kernel image name: pv-grub-hd0_1.04-x86_64.gz
Kernel release: 4.1.4-100.fc21.x86_64
Kernel version: #1 SMP Tue Aug 4 03:25:05 UTC 2015
Virtualization: paravirtual
When running ecryptfs-setup-private, I get the following error:
ERROR: Cannot get ecryptfs version, ecryptfs kernel module not loaded?
I tried sudo modprobe ecryptfs and got the following error:
modprobe: FATAL: Module ecryptfs not found.
This command succeeded while testing on the VMWare instance.
Looking at https://fedoraproject.org/wiki/Security_Features_Matrix it indicates that eCryptfs is an optional package in F21. Is this referring to the ecryptfs-utils package, or the kernel module, or both? Can eCryptfs be used on an Amazon EC2 instance, and if so, how do I get the kernel module installed?
Thanks
Ron Wagner
8 years, 3 months
Local DNSSEC resolver and Fedora cloud
by P J P
Hello all,
As we know, Fedora-23 Alpha release has just been announced. Which means, most of the proposed features which are approved for F23 are in reasonably good shape for us to try out.
One of the proposed system wide change is to install and enable local DNSSEC validating resolver across Fedora variants.
-> https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver
This features proposes to install unbound[1] DNSSEC resolver along with the dnssec-trigger[2] tool, which is used to dynamically configure the 'unbound' resolver. Upon successful setup, user would have the unbound[1] DNSSEC resolver listening on the 127.0.0.1:53 address. And the '/etc/resolv.conf' would point to this server as the designated 'nameserver' for the system.
Both unbound[1] & dnssec-trigger[2] packages are available in Fedora since long. And the proposed feature solution is known to work well for majority of the users. Currently work is in progress to ensure that the proposed feature works seamlessly well across all variants and addresses all use-cases for the Fedora users.
The feature has been approved for the upcoming F23 release; But we need affirmation from the individual working groups to install and enable this feature in the respective variants.
-> https://bugzilla.redhat.com/show_bug.cgi?id=1203950
The affirmation would enable us to include the 'dnssec-trigger' & 'unbound' packages in the respective Fedora kickstart files.
Could we please have your(cloud-WG) consent to enable this feature on the Fedora cloud variant?
If you have any concerns/comments/suggestions please let us know here.
--
[1] https://unbound.net/
[2] http://www.nlnetlabs.nl/projects/dnssec-trigger/
[3] https://lists.fedoraproject.org/pipermail/cloud/2015-July/005590.html
Thank you.
---Regards
-P J P
http://feedmug.com
8 years, 3 months
Re: Fedora Atomic Web site
by Joe Brockmeier
On 08/11/2015 03:09 PM, Robert Mayr wrote:
>
> I remember we talked a bit about this on IRC but this topic needs to be
> discussed further indeed.
> I'm actually traveling to Rochester, so if you (and all involved) are
> there I'm happy to talk about it.
Excellent. Let's chat in person and then carry back a summary to the
list. Any other folks at Flock are welcome to join in - and if anybody
not attending has an interest in working on this please let us know.
Thanks,
jzb
--
Joe Brockmeier | Community Team, OSAS
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
8 years, 3 months
Re: Fedora Atomic Web site
by Joe Brockmeier
----- Original Message -----
> From: "S.Kemter" <sirko.kemter(a)gmail.com>
> To: "Joe Brockmeier" <jzb(a)redhat.com>, "Fedora Marketing team" <marketing(a)lists.fedoraproject.org>
> Cc: "Robert Mayr" <robyduck(a)fedoraproject.org>, cloud(a)lists.fedoraproject.org, websites(a)lists.fedoraproject.org
> Sent: Wednesday, August 12, 2015 7:45:34 AM
> Subject: Re: Fedora Atomic Web site
>
> Hi,
>
> Joe, Matt came a while ago to us with it and we said, he should put that
> into design clinic we have at flock anyway, that is what we thought this
> "worshop" for.
I guess we had some gaps in communication there, I didn't know this was on an agenda specifically for Flock.
This is the Friday workshop at 5? I'll actually be heading out slightly before that, unfortunately.
Best,
jzb
--
Joe Brockmeier | Community Team, OSAS
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
8 years, 3 months
Re: F23 alpha release announcement
by Joe Brockmeier
Hey all,
I've filled it out a bit, but it could use some love. I'm struggling a bit to think of specifics for the workstation, cloud, and server releases. Any help much appreciated.
----- Original Message -----
> From: "Matthew Miller" <mattdm(a)fedoraproject.org>
> To: jzb(a)redhat.com, "Fedora Marketing team" <marketing(a)lists.fedoraproject.org>
> Cc: "Remy DeCausemaker" <rdecause(a)redhat.com>
> Sent: Monday, August 10, 2015 8:38:55 PM
> Subject: Re: F23 alpha release announcement
>
> On Mon, Aug 10, 2015 at 08:10:30PM -0400, Joe Brockmeier wrote:
> > Checking in on this - I know Gabriele and other folks had done a lot of
> > work on the talking points and such last week or so - but I don't know
> > if we have a F23 alpha release draft anywhere.
> > We're pretty close to the release (10 a.m. Eastern tomorrow) so I had a
> > mild panic this evening that we may be missing it. Or maybe I missed it
> > in the flurry of emails.
> > I can *probably* bang something out tomorrow morning early, but I'll be
> > getting ready for Flock and would prefer not to duplicate effort.
>
> I started a stub at
> https://fedoraproject.org/wiki/F23_Alpha_release_announcement
>
>
>
> --
> Matthew Miller
> <mattdm(a)fedoraproject.org>
> Fedora Project Leader
>
--
Joe Brockmeier | Community Team, OSAS
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
8 years, 3 months