Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693366 - No limit for /var/lib/docker - quota can be ignored
Summary: No limit for /var/lib/docker - quota can be ignored
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 16:25 UTC by Vladislav Walek
Modified: 2019-03-28 07:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Vladislav Walek 2019-03-27 16:25:32 UTC
Document URL: 

https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html#node-config-volume-config

Section Number and Name: 

Describe the issue: 

the problem is that, even if quota are set on the /var/lib/origin directory, the user running application can overwrite it when creating volume in the docker file.
Then the volume is created in /var/lib/docker where no quota is set.

This could be issue due the users can ignore any quota and mess up the node.

How reproducible:
- set the quota for the OpenShift as per docs [1]
- create image from dockerfile with VOLUME set
- deploy the image
- create big file under the volume
- check the OpenShift - the volume is mounted under /var/lib/docker without any quota

Suggestions for improvement: 
the volume is created under /var/lib/docker and ignoring the quota set for /var/lib/origin
if the quota is set, should be respected under the whole cluster
Configure the docs to set the quota as well as for /var/lib/docker

This could be potential issue when running the cluster for your customers. As the devs who are creating the images, can overwrite the quota with simply adding volume in the docker file.
The expectation is that for storage the PV and PVC should be used, but VOLUME can be used too.
The workaround for that is also set the grpquota for /var/lib/docker

[1] https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html#node-config-volume-config


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