| Summary: | Default docker-distribution.service file doesn't work as lack of subcommand | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Luwen Su <lsu> |
| Component: | docker-distribution | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | Keywords: | Extras, ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | docker-distribution-2.4.0-2.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-12 14:52:34 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: | |
|
Description
Luwen Su
2016-04-26 06:52:44 UTC
thanks, I'll update! Verified in docker-distribution-2.4.0-2.el7.x86_64.
Fill in a full testing steps for reference:
1.The registry can start by default config
install docker-distribution and start the service
#service docker-distribution start
2.Configuration config.yml with enabling tls function:
#cat /etc/docker-distribution/registry/config.yml
version: 0.1
log:
fields:
service: registry
storage:
cache:
blobdescriptor: inmemory
filesystem:
rootdirectory: /var/lib/registry
http:
addr: :5000
headers:
X-Content-Type-Options: [nosniff]
tls:
certificate: /root/certs/domain.crt
key: /root/certs/domain.key
health:
storagedriver:
enabled: true
interval: 10s
threshold: 3
Make self-signed ca and crt:
#mkdir -p certs && openssl req -newkey rsa:4096 -nodes -sha256 -keyout certs/domain.key -x509 -days 365 -out certs/domain.crt
#mkdir -p /etc/docker/certs/myregistrydomain.com:5000/
#cp certs/domain.crt /etc/docker/certs/myregistrydomain.com:5000/ca.crt
Start docker-distribution and docker service.
Then a martix pull and push testing covered.
* 1.10 docker(docker-latest) pull and push
* 1.9 docker pull and push
* HostA:1.10 docker push, HostB: 1.9 docker pull and vice verse.
Move to verified
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://rhn.redhat.com/errata/RHBA-2016-1058.html |