RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1314159 - [DOCS] Document per container rootfs sizes & default
Summary: [DOCS] Document per container rootfs sizes & default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-RHEL-Atomic
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Yoana Ruseva
QA Contact: Vivek Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 05:43 UTC by Vikram Goyal
Modified: 2023-09-14 03:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-11 20:22:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vikram Goyal 2016-03-03 05:43:48 UTC
In 7.2.3, the default rootfs size is set to (10 or 20 GB).

Document for this user story:

* the default rootfs size
* how to set the container rootfs size as a docker CLI option
* mention that the user can only increase the size and not decrease it

Likely Guide:
Getting Started with Containers

Trello Card:
https://trello.com/c/ViUfjt3y/23-storage-devmapper-per-container-rootfs-sizes-default

Comment 3 Yoana Ruseva 2016-06-22 17:35:52 UTC
Documented in: 

7.7. Increasing the Base Device Size

https://access.qa.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#managing_storage_with_docker_formatted_containers

Not everything mentioned in the Trello card has been implemented yet, so I documented it as it is today.

Comment 4 Vivek Goyal 2016-06-22 20:58:40 UTC
@yoana, I clicked on the link and did not see your changes. What am I missing.

Shishir, can you please also review the changes.

Comment 5 Vikram Goyal 2016-06-23 22:42:44 UTC
Hey Vivek,

This should be available here: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#increasing_the_base_device_size

Let me know if you can see the changes?

Comment 6 Yoana Ruseva 2016-07-11 20:22:06 UTC
Documented in 7.7. Increasing the Base Device Size:

https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#increasing_the_base_device_size

Closing this bug. Vivek, reopen if the text needs more work. If it needs substantial rework or there are new features, please open a new bug for 7.2.6.

Comment 7 Red Hat Bugzilla 2023-09-14 03:18:52 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.