<div dir="ltr"><div class="gmail_default" style="font-size:small">A lean metadata + tooling container is very appealing. Has this been achieved as a proof of concept? I'd love to see a README with an image pushed to the docker hub. ;)<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 20, 2015 at 10:15 AM, Alec Benson <span dir="ltr"><<a href="mailto:albenson@redhat.com" target="_blank">albenson@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Correct, we will only need to put the static binary inside the
container to be able to use the program. The Nulecule-Go does import
some additional Golang libraries like Logrus, go-yaml, and
Codegangsta CLI. Dan Veillard's concern is that if users want to
build from source, these dependent libraries are hard to get in RPM
form in CentOS (However, they are available in Fedora). <br>
<br>
But since, as you pointed out, the goal is to be able to ship this
binary statically in a container, I think that trying to get these
golang libraries into CentOS form creates more work for package
maintainers and doesn't provide much additional benefit. That is my
opinion, but it sounds like if we do end up wanting to add these
libraries to CentOS, we should be able to do that as well.<span class="HOEnZb"><font color="#888888"><br>
<br>
Alec <br></font></span><div><div class="h5">
<br>
<div>On 08/20/2015 09:54 AM, Daniel J Walsh
wrote:<br>
</div>
<blockquote type="cite">
My goal with creating nulecule go version, was to be able to ship
a static go binary inside of a container. And that would<br>
be the only thing in the container. I was hoping we could do this
without an OS. Their would be no RHEL/Fedora/Centos version.<br>
<br>
Does nulecule need any other programs in the container?<br>
<br>
<div>On 08/19/2015 11:21 AM, Lokesh
Mandvekar wrote:<br>
</div>
<blockquote type="cite">
<pre>On Wed, Aug 19, 2015 at 01:30:14PM -0400, Alec Benson wrote:
</pre>
<blockquote type="cite">
<pre>CC Lokesh Mandvekar
On 08/18/2015 11:14 PM, Daniel Veillard wrote:
</pre>
<blockquote type="cite">
<pre> I would be tempted to move it under Atomic indeed. My main question
is about the deployment model, there is a number of dependencies, are
they available in Fedora and CentOS, I would assume no, so this mean we
need to ship it as a container for people to be able to start using it.
I would say move to Atomic once we have that sorted out and don't leave
the coming users to sort out how to install the deps. Because if they
fail it's unlikely they will give it a second chance later.
</pre>
</blockquote>
</blockquote>
<pre>Users will never need to care about those deps unless they gotta care about
actually building nulecule.
If needed, those deps can be gotten into CentOS pretty quickly. Jan Chaloupka has authored
'gofed' which takes care of a lot of things. Else, we could (dare I say, should)
always use the bundled upstream deps (if upstream bundles them that is) :)
Others may (and probably will) disagree, but I strongly feel
we should prefer using upstream bundled golang libs (whenever available) than
depend on rpms. I feel golang-* rpms are just added labor which
nobody (other than pkg owners) cares about and which provide little to no benefit as _all_ they
end up doing is removing the bundled source and replacing it with the rpm
installed sources. Though using rpm-ed golang deps sounds so amazing in principle,
in reality there are some PITAs. Interesting read available
here: <a href="https://fedorahosted.org/fpc/ticket/382" target="_blank">https://fedorahosted.org/fpc/ticket/382</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>Daniel
On Tue, Aug 18, 2015 at 04:20:57PM +0200, Vaclav Pavlin wrote:
</pre>
<blockquote type="cite">
<pre>I forgot to add Alec to CC and paste a link to the repo:
<a href="https://github.com/alecbenson/nulecule-go" target="_blank">https://github.com/alecbenson/nulecule-go</a>
Sorry:)
V.
On Tue, Aug 18, 2015 at 4:17 PM, Vaclav Pavlin <a href="mailto:vpavlin@redhat.com" target="_blank"><vpavlin@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hey,
Alec asked me if his golang implementation of Nulecule could be moved
under Project Atomic github organization.
I haven't enough time to test it properly yet, but it might be worth
discussing it on a cabal call tomorrow.
Any thoughts, objections?
Thanks,
Vašek
--
Architect - Senior Software Engineer
Developer Experience
Brno, Czech Republic
Phone: <a href="tel:%2B420%20739%20666%20824" value="+420739666824" target="_blank">+420 739 666 824</a>
</pre>
</blockquote>
<pre>--
Architect - Senior Software Engineer
Developer Experience
Brno, Czech Republic
Phone: <a href="tel:%2B420%20739%20666%20824" value="+420739666824" target="_blank">+420 739 666 824</a>
_______________________________________________
Container-tools mailing list
<a href="mailto:Container-tools@redhat.com" target="_blank">Container-tools@redhat.com</a>
<a href="https://www.redhat.com/mailman/listinfo/container-tools" target="_blank">https://www.redhat.com/mailman/listinfo/container-tools</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Container-tools mailing list
<a href="mailto:Container-tools@redhat.com" target="_blank">Container-tools@redhat.com</a>
<a href="https://www.redhat.com/mailman/listinfo/container-tools" target="_blank">https://www.redhat.com/mailman/listinfo/container-tools</a>
</pre>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Container-tools mailing list
<a href="mailto:Container-tools@redhat.com" target="_blank">Container-tools@redhat.com</a>
<a href="https://www.redhat.com/mailman/listinfo/container-tools" target="_blank">https://www.redhat.com/mailman/listinfo/container-tools</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Container-tools mailing list<br>
<a href="mailto:Container-tools@redhat.com">Container-tools@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/container-tools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/container-tools</a><br>
<br></blockquote></div><br></div>