<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 03/19/2015 09:25 AM, Daniel J Walsh
wrote:<br>
</div>
<blockquote cite="mid:550ADC76.8020906@redhat.com" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
Scott we found an interesting problem with libvirt protections on
/dev/kvm. If you run this container on an atomic machine, the
device has the wrong protections. You need to add chmod 666
/dev/kvm to make it work, or<br>
<br>
chmod 660 /dev/kvm<br>
chown root:qemu /dev/kvm<br>
</blockquote>
<br>
ack. I will go in and make the changes.<br>
<br>
<blockquote cite="mid:550ADC76.8020906@redhat.com" type="cite"> <br>
I think this would break on other machines that do not have
libvirt installed on the host.<br>
<br>
<br>
On 03/19/2015 10:20 AM, Scott Collier wrote:<br>
<span style="white-space: pre;">><br>
><br>
> On 03/11/2015 09:40 AM, Major Hayden wrote:</span><br>
<blockquote type="cite">On 03/11/2015 09:23 AM, Joe Brockmeier
wrote:<br>
>>> I'm CC'ing Scott b/c, if I'm not mistaken, he's
done quite a lot of<br>
>>> the work so far on the Dockerfiles - but also, I
think he's looking<br>
>>> for assistance there in keeping the effort going.<br>
I'll be glad to help maintain/update those Dockerfiles if
needed, Scott.<br>
<br>
> Thanks Major. Here's a summary of things I think we should
be looking at in general, not just Dockerfile maintenance:<br>
<br>
> 1. Ensuring dnf support on Fedora 22 images. This means
figuring out how to manage dockerfiles in a manner that both dnf
or yum can work. For example, the FROM line will determine what
package installation method we will use. If it's FROM
fedora:rawhide, should use dnf, if it's FROM fedora:21, should
use yum. Just need to think that through and how we want to
handle. I haven't played around with dnf yet.<br>
<br>
> 2. Need READMEs for the libvirt images:<br>
<br>
> <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt">https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt</a><br>
>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvirt">https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvirt</a><br>
<br>
> 3. Need some extra eyes on all PRs and images that come
in. Might be good to require a +1 from two maintainers before
merging a request? Thoughts?<br>
<br>
> 4. I'd like to set up some CI on these where and if it
makes sense. Some triggers: docker package updates, Dockerfile
updates, etc... Something simple: build the image, run the
image, test for an expected result.<br>
<br>
> 5. Does it make sense to add some kubernetes support /
examples to these? I know not all of these apps are "scalable"
or usable in a production k8s cluster, per se, but dropping in a
yaml file for a few select images, so people can explore and
learn wouldn't hurt. It could sit right by the Dockerfile.
People could build the image, and deploy in a k8s environment.<br>
<br>
> 6. Now that the LABEL patch has been (or will be merged)
into Docker, we'll want people to start testing the LABEL
functionality in fedora-dockerfiles and take advantage of that
with the new atomic package. We'll want to abstract away any
complex docker install / docker run commands moving forward.
This will take some effort. This will be very helpful on an any
host with the atomic tool.<br>
<br>
> Anything else? Thoughts?<br>
<br>
<br>
<br>
</blockquote>
<span style="white-space: pre;">>>
_______________________________________________<br>
>> cloud mailing list<br>
>> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
>> <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://admin.fedoraproject.org/mailman/listinfo/cloud">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
>> Fedora Code of Conduct: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a><br>
><br>
> _______________________________________________<br>
> cloud mailing list<br>
> <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
> <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://admin.fedoraproject.org/mailman/listinfo/cloud">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
> Fedora Code of Conduct: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a></span><br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cloud mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a>
<a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/mailman/listinfo/cloud">https://admin.fedoraproject.org/mailman/listinfo/cloud</a>
Fedora Code of Conduct: <a class="moz-txt-link-freetext" href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a>
</pre>
</blockquote>
<br>
</body>
</html>