Hey all,
So dgilmore pointed out that f22 docker images will not have yum installed - which means we need to update the Dockerfiles for f22 to use dnf and not yum.
We probably ought to go through and sanity-check them all to ensure they work with the f22 image as well before, say, beta.
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
Best,
jzb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
- -- Major Hayden
The Dockerfiles are on Github IIRC - if I fork / pull request for my PostGIS one, is there a chance it'll get in the release?
On Wed, Mar 11, 2015 at 7:40 AM, Major Hayden major@mhtx.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Major Hayden -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJVAFPcAAoJEONAdDQ9I/mwSKEH/2axXPtLKik7QII+/e6XzrJQ LY8jeSXHMyFqaa86bhTI8pcp7fC05oXWCxkmg23SMhgAG7Ls+n39YXERzvnXx2FO kGX59Kb9wcZ5YhbDZw53yRQeqDniRc9mb16qJvnuQ901gNcUWD9xKQ+P98HfAKT5 UY9WaSWETiT6oZwATlrMROM/2zUHUaEyBK8WvWTgVZATc4fijE9h3jutrZ1/BCYB r038olR/kC0UHrGrY7EQB2TP5ECp1+ygbFzN0I6R63OivM//1yZy83BGP07p81QV QlR/wsiJFWPOQPzBzeJ2ZYNGjdt8luDjBLV3nG2p4V4w0ikItilkZTiHp337ih8= =MmjD -----END PGP SIGNATURE----- _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On 03/11/2015 09:40 AM, Major Hayden wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Thanks Major. Here's a summary of things I think we should be looking at in general, not just Dockerfile maintenance:
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.
2. Need READMEs for the libvirt images:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvi...
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?
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.
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.
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.
Anything else? Thoughts?
Major Hayden -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJVAFPcAAoJEONAdDQ9I/mwSKEH/2axXPtLKik7QII+/e6XzrJQ LY8jeSXHMyFqaa86bhTI8pcp7fC05oXWCxkmg23SMhgAG7Ls+n39YXERzvnXx2FO kGX59Kb9wcZ5YhbDZw53yRQeqDniRc9mb16qJvnuQ901gNcUWD9xKQ+P98HfAKT5 UY9WaSWETiT6oZwATlrMROM/2zUHUaEyBK8WvWTgVZATc4fijE9h3jutrZ1/BCYB r038olR/kC0UHrGrY7EQB2TP5ECp1+ygbFzN0I6R63OivM//1yZy83BGP07p81QV QlR/wsiJFWPOQPzBzeJ2ZYNGjdt8luDjBLV3nG2p4V4w0ikItilkZTiHp337ih8= =MmjD -----END PGP SIGNATURE----- _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
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
chmod 660 /dev/kvm chown root:qemu /dev/kvm
I think this would break on other machines that do not have libvirt installed on the host.
On 03/19/2015 10:20 AM, Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote: On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Thanks Major. Here's a summary of things I think we should be
looking at in general, not just Dockerfile maintenance:
- 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.
- Need READMEs for the libvirt images:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvi...
- 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?
- 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.
- 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.
- 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.
Anything else? Thoughts?
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On 03/19/2015 09:25 AM, Daniel J Walsh wrote:
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
chmod 660 /dev/kvm chown root:qemu /dev/kvm
ack. I will go in and make the changes.
I think this would break on other machines that do not have libvirt installed on the host.
On 03/19/2015 10:20 AM, Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote: On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Thanks Major. Here's a summary of things I think we should be
looking at in general, not just Dockerfile maintenance:
- 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.
- Need READMEs for the libvirt images:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvi...
- 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?
- 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.
- 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.
- 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.
Anything else? Thoughts?
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Thu, Mar 19, 2015, at 10:25 AM, Daniel J Walsh wrote:
I think this would break on other machines that do not have libvirt
installed on the host.
Right, it's a problem orthogonal to the Atomic Host.
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.
In general, Docker containers that want to access host devices may need to replicate some of the logic from the host udev.
On Thursday, March 19, 2015 09:20:55 AM Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Thanks Major. Here's a summary of things I think we should be looking at in general, not just Dockerfile maintenance:
- 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.
- Need READMEs for the libvirt images:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvi rt
- 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?
- 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.
- 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.
- 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.
Anything else? Thoughts?
I would like to build some docker things for ARM, though right now we can not do it officially, we do not have machines in phx to build docker base images. being able to support arm would be awesome also.
Dennis
On 03/19/2015 07:50 PM, Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going.
I'll be glad to help maintain/update those Dockerfiles if needed, Scott.
Thanks Major. Here's a summary of things I think we should be looking at in general, not just Dockerfile maintenance:
- 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.
- Need READMEs for the libvirt images:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/libvirt https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/libvi...
- 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?
- 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.
- 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.
+1. Having k8 config files would help others. As of now I am trying to understand k8s. I am interested to contribute towards the k8s files.
-Lala
- 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.
Anything else? Thoughts?
Major Hayden -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJVAFPcAAoJEONAdDQ9I/mwSKEH/2axXPtLKik7QII+/e6XzrJQ LY8jeSXHMyFqaa86bhTI8pcp7fC05oXWCxkmg23SMhgAG7Ls+n39YXERzvnXx2FO kGX59Kb9wcZ5YhbDZw53yRQeqDniRc9mb16qJvnuQ901gNcUWD9xKQ+P98HfAKT5 UY9WaSWETiT6oZwATlrMROM/2zUHUaEyBK8WvWTgVZATc4fijE9h3jutrZ1/BCYB r038olR/kC0UHrGrY7EQB2TP5ECp1+ygbFzN0I6R63OivM//1yZy83BGP07p81QV QlR/wsiJFWPOQPzBzeJ2ZYNGjdt8luDjBLV3nG2p4V4w0ikItilkZTiHp337ih8= =MmjD -----END PGP SIGNATURE----- _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Wed, Mar 11, 2015, at 10:23 AM, Joe Brockmeier wrote:
Hey all,
So dgilmore pointed out that f22 docker images will not have yum installed - which means we need to update the Dockerfiles for f22 to use dnf and not yum.
Personally, this feels like a lot of pain for little gain to me. We could install dnf-yum by default? What do others think?
On Thu, Mar 19, 2015 at 11:10:33AM -0400, Colin Walters wrote:
So dgilmore pointed out that f22 docker images will not have yum installed - which means we need to update the Dockerfiles for f22 to use dnf and not yum.
Personally, this feels like a lot of pain for little gain to me. We could install dnf-yum by default? What do others think?
See discussion at https://fedorahosted.org/fesco/ticket/1312
On Thu, Mar 19, 2015, at 11:19 AM, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 11:10:33AM -0400, Colin Walters wrote:
So dgilmore pointed out that f22 docker images will not have yum installed - which means we need to update the Dockerfiles for f22 to use dnf and not yum.
Personally, this feels like a lot of pain for little gain to me. We could install dnf-yum by default? What do others think?
See discussion at https://fedorahosted.org/fesco/ticket/1312
Thanks, per that discussion:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=961b78fbd89...
(In case anyone was curious, first I had to shave a few yaks in the previous commits)
Looking at the fedora-dockerfiles RPM for Fedora 24, it looks like the switch from YUM to DNF still hasn't happened. This is causing errors during docker runs that obviously aren't a big deal but it seems like an easy fix now to just swap the yums out for dnfs.
Has this been talked about recently? This was the latest thread I could find.
-
Colin Walters -
Daniel J Walsh -
Dennis Gilmore -
Joe Brockmeier -
Kodiak Firesmith -
Lalatendu Mohanty -
M. Edward (Ed) Borasky -
Major Hayden -
Matthew Miller -
Scott Collier