Bug 1305634 - [RFE] provide a smaller container for just man pages
Summary: [RFE] provide a smaller container for just man pages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-tools-container
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eliska Slobodova
QA Contact: atomic-bugs@redhat.com
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 19:08 UTC by Micah Abbott
Modified: 2020-12-15 07:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:40:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Micah Abbott 2016-02-08 19:08:47 UTC 
Description of problem:

The current 'rhel-tools' container is the preferred way of accessing man pages for the RHEL Atomic Host.  Unfortunately, it weighs in at 1.159 GB, which is quite large if you just need access to man pages.

We could still provide the 'rhel-tools' container with the man pages (or perhaps link containers).
Comment 1 Daniel Walsh 2016-02-08 19:13:54 UTC 
Could we start to put the RHEL-tools container into a layered mode, where we could make the man pages as lower layer.  Rather then building a totally separate container image.
Comment 2 Micah Abbott 2016-02-08 19:18:28 UTC 
Sounds like a good approach; it also means we don't have to track separate deliverables.
Comment 4 Eliska Slobodova 2016-04-05 07:40:55 UTC 
Hi guys, OSBS squashes images, so I believe "layered mode" wouldn't work here.
Comment 5 Daniel Walsh 2016-10-18 16:57:30 UTC 
Any one examined why the RHEL tools container is so HUGE?
Comment 8 RHEL Program Management 2020-12-15 07:40:01 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.