pulp supports removal of specific images/layers. Removing one from the
middle of an ancestry line definitely breaks its children permanently.
Given a rhel base image, a generic python web app image based on that, and
then a custom app image as the "leaf" of your tree, assume you need to
patch a
On Wed, Sep 2, 2015 at 4:27 PM, Scott McCarty wrote:
> All,
> I had an epiphany the other day, that I would love to be able to
> synchronize an entire stack:
>
> 1. RPM Content for OS
> 2. Puppet Modules to configure
> 3. Docker Images built from the above
> 4. RPM
On 09/03/2015 09:50 AM, Michael Hrivnak wrote:
On Wed, Sep 2, 2015 at 4:27 PM, Scott McCarty > wrote:
All,
I had an epiphany the other day, that I would love to be able
to synchronize an entire stack:
1. RPM Content for OS
Scott McCarty wrote:
> - Absolutely, is there a guide somewhere on how to start this off?
I don't believe we have any formal process documented for writing a
story, so I'll write some high level stuff here:
0) Use Redmine to file a new issue:
https://pulp.plan.io/projects/pulp/issues/new
1)
Sent from my Verizon Wireless 4G LTE smartphone
Scott McCarty, RHCA
Technical Marketing Manager: Containers
Email: smcca...@redhat.com
Phone: 312-660-3535Cell: 330-807-1043
Web: http://crunchtools.com
Original message From: Randy Barlow Date:
9/3/2015
Michael Hrivnak wrote:
This is conceptually the same with v1 and v2; they've mostly just
changed terminology.
To clarify a little, in pulp-docker-2.0.0 (not released or even alpha
built yet), we are going to have a new data type called a Manifest.
Rather than interacting with and promoting
You can find the latest Pulp 2.6.3 Release Candidate in the usual location [0].
- Dennis
[0] https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.6/
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list