<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I was referring to the first one. I'm
trying to get used to the notion of a package management system
that runs underneath or beside the operating system's. <br>
<br>
On 9/18/17 5:25 PM, lnxgnome wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ee2cba80-2105-d195-1bbd-43e9b4eacbf3@hopnet.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Jeff, <br>
</p>
<p> Are you asking about Anaconda <a
class="moz-txt-link-freetext" href="https://www.anaconda.com/"
moz-do-not-send="true">https://www.anaconda.com/</a> or
Anaconda <a class="moz-txt-link-freetext"
href="https://fedoraproject.org/wiki/Anaconda"
moz-do-not-send="true">https://fedoraproject.org/wiki/Anaconda</a>
?<br>
</p>
For the first, there is... <a class="moz-txt-link-freetext"
href="https://github.com/ContinuumIO/docker-images/tree/master/anaconda"
moz-do-not-send="true">https://github.com/ContinuumIO/docker-images/tree/master/anaconda</a><br>
For the second, there is...
<a class="moz-txt-link-freetext"
href="http://atodorov.org/blog/2015/10/28/building-docker-images-with-anaconda/"
moz-do-not-send="true">http://atodorov.org/blog/2015/10/28/building-docker-images-with-anaconda/</a><br>
<br>
<br>
<div class="moz-cite-prefix">On 20170918 12:49 PM, Jeff Hubbs
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6b96cb76-6f69-e3d3-34a5-e2474fbeb9cf@att.net">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div class="moz-cite-prefix">Can someone help characterize for
me how Anaconda fits into this whole container business?<br>
<br>
On 9/18/17 11:52 AM, Jim Kinney wrote:<br>
</div>
<blockquote type="cite"
cite="mid:E6E22DEC-AABE-4ECF-B980-772C034A71A4@gmail.com">I'm
very close to the point of isolating my docker junkies in
every possible way and letting their stuff get broken into.
That will be the only way to get the political leverage to be
able tell a PhD faculty "NO. It ALL runs through me and
upstream university security. No exception."<br>
<br>
<div class="gmail_quote">On September 18, 2017 9:34:37 AM EDT,
Solomon Peachy <a class="moz-txt-link-rfc2396E"
href="mailto:pizza@shaftnet.org" moz-do-not-send="true"><pizza@shaftnet.org></a>
wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<pre class="k9mail">On Mon, Sep 18, 2017 at 09:18:46AM -0400, Jerald Sheets wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> All containers should be curated by Systems. The Developers should
submit them for security scanning, or you should employ a DevSecOps
model for deployment. i.e., federate security scanning by providing
OS, App, transport, penetration, and network security testing as APIs
that devs can leverage instead of leaving them to security. Left to
their own devices, unreasonable deploy timelines set for them, and
golf-playing pointy-hairs with unreasonable ship date requirements,
it’ll never happen.
</blockquote>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> This should all be automated and part of a security CI/CD pipeline
without which a “pass” from the security field, cannot ever be
deployed into production. This is how we do it.
</blockquote>
The unspoken assumption here is that your needs are sufficient to make
this (completely necessary!) administrative overhead worthwhile.
Unfortunately, much like VMs before, most shops just "download an image"
from the likes of DockerHub and then deploy it, with no real thought
towards ongoing maintainence or security concerns. Because those cost
time/effort -- and therefore and money.
- Solomon </grumble></pre>
</blockquote>
</div>
<br>
-- <br>
Sent from my Android device with K-9 Mail. All tyopes are
thumb related and reflect authenticity. <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org" moz-do-not-send="true">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo/ale" moz-do-not-send="true">http://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo" moz-do-not-send="true">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
<p><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org" moz-do-not-send="true">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo/ale" moz-do-not-send="true">http://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo" moz-do-not-send="true">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>