9:21 a.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Final)
Component: Collaboration & Communication | Keywords: meeting
-------------------------------------------+-------------------------------
https://github.com/fedora-cloud/Fedora-Dockerfiles is
a) cool
b) useful
c) active
d) a great place for new contributors
We should popularize this. Articles, blog posts, wiki documentation, non-
wiki documentation, etc.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9:33 a.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by scollier):
I think that's a great idea. Opportunities for contributions:
a) Once we get the systemd in containers all figured out, we'll need to do
a massive conversion for all examples using supservisord.
b) Some of the Dockerfiles haven't been tested since < 1.0. Images have
been built, but not necessarily run and carefully looked at.
c) README's could be cleaned up a bit and standardized further
d) The examples are really single service focused. Would be cool to have
some folks tie together these services and create some complex apps for
demo / learning purposes. Then figure out some way to save that for
others to test.
e) and we are always looking for new examples / contributions!
Keep in mind, this feeds both the fedora-dockerfiles package as well as
some of the images on the Docker hub.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:31 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Changes (by jzb):
* cc: jzb@… (added)
Comment:
We can work this into the release announcement *if* we're confident that
the bulk of the dockerfiles are actually updated + good to go.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:2>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
3:23 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by scollier):
@jzb, I'm pretty confident on where we are with the files.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:3>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:23 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by dustymabe):
Random Question.. I feel like one goal of promoting these is to promote
F21/Atomic as well as their support of Docker. Should we wait to heavily
promote these until many of the dockerfiles have been updated to use
Fedora's official Docker base image (the first one being from F21) rather
than the F20 image created by Marek?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:4>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:33 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by mattdm):
Replying to [comment:4 dustymabe]:
Random Question.. I feel like one goal of promoting these is to
promote
F21/Atomic as well as their support of Docker. Should we wait to heavily
promote these until many of the dockerfiles have been updated to use
Fedora's official Docker base image (the first one being from F21) rather
than the F20 image created by Marek?
We should definitely do that update. I don't know how much we want to wait
based on that, though.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:5>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:13 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Changes (by jzb):
* status: new => assigned
* owner: => jzb
Comment:
Discussed during today's meeting. I'm taking this ticket and will come up
with a general plan for promoting these around the release and beyond.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:6>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:13 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by jzb):
Breaking this down into individual tickets.
Fedora Magazine Post: How to use dockerfiles -
https://fedorahosted.org/cloud/ticket/87
Social media: https://fedorahosted.org/cloud/ticket/88
Dockerfile section downloads page?
https://fedorahosted.org/cloud/ticket/89
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:7>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:28 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by jzb):
Potential articles / headlines:
"Fedora Images on Docker Hub"
"How to Contribute Dockerfiles - What's Needed?"
"Using CI to Build and Verify Dockerfiles"
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:8>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:41 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by scollier):
Potential articles / headlines:
"Connecting Services in Docker Images"
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:9>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:47 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by znmeb):
I'm just starting to look at the fedora-dockerfiles. I managed to get the
Firefox one running but it was a struggle - vnc in a Docker container's
non-trivial. The Redis and PostgreSQL ones are high on my list to get
working.
However, if the licensing and trademark folks don't have major issues with
it, you're welcome to use my 'osjourno-rd' project as an example. See
http://www.rstudio.com/about/trademark/ for the IP issues and
https://registry.hub.docker.com/u/znmeb/osjourno-rd/ for the project
itself.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:10>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:01 p.m.
#84: publicize fedora-dockerfiles
-------------------------------------------+-------------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 21
Component: Collaboration & Communication | (Final)
Keywords: meeting | Resolution:
-------------------------------------------+-------------------------------
Comment (by jzb):
Posted the 101-level piece today on Fedora Magazine, promoted on Twitter.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:11>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:02 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles (was: publicize fedora-dockerfiles)
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Changes (by jzb):
* milestone: Fedora 21 (Final) => Fedora 22
Comment:
Unless someone screams "no" - I'm changing this ticket title to "care
and
feeding" to manage multiple issues related to Dockerfiles. (Old title
"publicize fedora-dockerfiles")
Adding an issue:
* f22 docker image does not have yum. We need to deal with updating all
images to use dnf instead of yum.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:12>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:50 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by znmeb):
I'll sign up to do testing for sure, starting with the PostgreSQL one.
That's on my roadmap with PostGIS added. The "Firefox" one would be nice
to have but PostgreSQL/PostGIS is the only one I know I'll need.
I don't see the F22 Docker image on Docker Hub - the Rawhide image is
there, however, and IIRC it has yum and not dnf. So a subtask to this
issue is getting an F22 image posted to Docker Hub.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:13>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:25 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by jzb):
As discussed today in Cloud Meeting - we're still more or less where we
were six months ago. We need to break these out in separate tickets and
start working them that way. Will revisit this once we have a new repo
tested / broken out for centos/fedora dockerfiles.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:14>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:23 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by lalatendu):
For maintaining the dockerfiles we need to create branches for Fedora
releases so that they can be maintained without effecting each other. I
have sent the suggestion on cloud sig mailing list [1]. The thread should
give enough information about the idea.
[1] https://lists.fedoraproject.org/pipermail/cloud/2015-July/005603.html
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:15>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10:08 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by scollier):
Replying to [comment:15 lalatendu]:
For maintaining the dockerfiles we need to create branches for Fedora
releases so that they can be maintained without effecting each other. I
have sent the suggestion on cloud sig mailing list [1]. The thread should
give enough information about the idea.
[1]
https://lists.fedoraproject.org/pipermail/cloud/2015-July/005603.html
Created:
Master:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master
F21:
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/f21
F22
https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/f22
I have not made any changes to the branches yet. We need someone to test
the conversion to DNF. I also would like to bring up CI again here. That
would help immensely.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:16>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:38 a.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by adimania):
Replying to [comment:16 scollier]:
We need someone to test the conversion to DNF. I also would like to
bring up CI again here. That would help immensely.
What is the goal of CI?
If all we want is a way to try building the image from the dockerfile and
mark as successful if image is built, then I can write a script to look
for Dockerfile and do the needful. But if the idea is to check the sanity
of the image, for example, fire up containers from the image and check if
the image is working as '''expected''', then it can be a tough
deal.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:17>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
12:07 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by mattdm):
Replying to [comment:17 adimania]:
If all we want is a way to try building the image from the dockerfile
and mark as successful if image is built, then I can write a script to
look for Dockerfile and do the needful. But if the idea is to check the
sanity of the image, for example, fire up containers from the image and
check if the image is working as '''expected''', then it can be a
tough
deal.
Not speaking for Scott, but I it'd be very helpful to start with that
simple build check, and then go more complicated for there. (Let's not let
complicated end goals stop us from doing the quick things now.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:18>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
12:39 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by adimania):
I wrote this [https://gist.github.com/adimania/6965be099904433f626f
script] to build all the images from dockerfile and ran it on the master
branch of the git repo. I can modify it to run on any branch. The
following failed to build:
{{{
firefox failed to build
libvirt failed to build
mesos failed to build
mesos failed to build
haskell failed to build
hadoop failed to build
mysql failed to build
}}}
I checked the build logs and almost all of them failed due to broken
package dependencies. [[BR]]
Please have a look at the script and let me know if I am doing anything
wrong. I would try to fix some of these Dockerfiles but I have no
experience with Hadoop or Haskell or Mesos. So I might not be able to fix
all of them.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:19>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:19 a.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: assigned
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution:
Keywords: meeting |
-------------------------------------------+------------------------
Comment (by adimania):
I have been working on f22 branch to move it to dnf and to clear out
issues in the build test that I wrote. For this weekend, here are the
findings for f22 branch:
* replaced yum with dnf
* forcing the use of fedora 22 for f22 branch. The current Dockerfiles
have various images hardcoded, including rhel in one of the files.
* ran the build test from
https://gist.github.com/adimania/6965be099904433f626f. Following images
failed to build due to package dependencies:
* firefox
* container-best-practices
* haskell
* I have removed pdftk since that is no longer packaged for f22.
The pull request for the changes is [https://github.com/fedora-cloud
/Fedora-Dockerfiles/pull/133 here]
PS: Note that I had to run a couple of failed cases manually. There is a
corner case which is being missed in the build script. I will fix that
shortly.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:20>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
12:30 p.m.
New subject: [cloud] #84: Care and Feeding, Fedora Dockerfiles
#84: Care and Feeding, Fedora Dockerfiles
-------------------------------------------+------------------------
Reporter: mattdm | Owner: jzb
Type: task | Status: closed
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Resolution: fixed
Keywords: meeting |
-------------------------------------------+------------------------
Changes (by roshi):
* status: assigned => closed
* resolution: => fixed
Comment:
This ticket has been split into more granular tickets (Thanks scollier!).
Closing.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/84#comment:21>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
3132
days inactive
3448
days old
21 comments
1 participants
participants (1)
-
Fedora Cloud Trac Tickets