Bug 1511400
| Summary: | openshift ex dockergc can't clean image database if docker use devicemapper | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | DeShuai Ma <dma> |
| Component: | Node | Assignee: | Seth Jennings <sjenning> |
| Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.7.0 | CC: | aos-bugs, decarr, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-28 14:11:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
DeShuai Ma
2017-11-09 10:01:16 UTC
I believe this was a limitation that we all agreed was acceptable since this feature is targeted for Online deployment when cri-o is the runtime. In that case we would be running docker with overlay. Derek is this correct? That being said, it might not be too difficult to make it work for devicemapper as well if we can extract the usage data directly from docker. Do we want to try that? Not supporting usage of devicemapper is fine ATM. Let's explicitly doc the set of storage drivers we can support with the experimental command. Verify on ocp-3.9 # oc version oc v3.9.0-0.16.0 kubernetes v1.9.0-beta1 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://xxxx:8443 openshift v3.9.0-0.16.0 kubernetes v1.9.0-beta1 There is "Only the overlay2 docker storage driver is supported at this time." in 'oc ex -h' //detail: # oc ex dockergc -h Perform garbage collection to free space in docker storage If the OpenShift node is configured to use a container runtime other than docker, docker will still be used to do builds. However OpenShift itself may not manage the docker storage since it is not the container runtime for pods. This utility allows garbage collection to do be done on the docker storage. Only the overlay2 docker storage driver is supported at this time. Usage: oc ex dockergc [NAME] [options] Examples: # Perform garbage collection with the default settings ocex dockergc Options: --dry-run=false: If true, show the result of the operation without performing it. --image-gc-high-threshold=80: The percent of disk usage after which image garbage collection is always run. --image-gc-low-threshold=60: The percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. --minimum-ttl-duration=1h0m0s: Minimum age for a container or unused image before it is garbage collected. Examples: '300ms', '10s' or '2h45m'. -o, --output='': Output results as yaml or json instead of executing, or use name for succint output (resource/name). -a, --show-all=false: When printing, show all resources (default hide terminated pods.) --show-labels=false: When printing, show all labels as the last column (default hide labels column) --sort-by='': If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string. --template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. Use "oc options" for a list of global command-line options (applies to all commands). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489 |