Bug 1311452
Summary: | The docker registry does not work well with special volume | ||
---|---|---|---|
Product: | OKD | Reporter: | zhou ying <yinzhou> |
Component: | Image Registry | Assignee: | Paul Weil <pweil> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wei Sun <wsun> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.x | CC: | aos-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-12 17:10:08 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
zhou ying
2016-02-24 09:52:52 UTC
Using --volume means that you're trying to change the default directory for storage. This should be accompanied by a change in the config.yaml for the image or a change in the deployment config to add the env var - name: REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY value: /registrytest otherwise, it will continue to try to use the default /registry as the basedir and it will not be mounted as an emptydir volume which includes the correct write permissions. That is what is giving the "permission denied" error. Hi Paul: Thanks ! I add the env var by: `oc env dc/docker-registry REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/registrytest` works well . Will update the cases. |