request for change: support docker private repository with self-certificate and password

Bug #1584086 reported by Peng Wu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
murano-apps
New
Wishlist
Unassigned

Bug Description

We are testing a private Docker registry using a self-certificate with password protection. Thus we would like to have the ability to run the standalone docker host with recorded certificate and id/password. Manually it would need to run one-time commands similar to the following on the docker standalone host:

mkdir -p /etc/docker/certs.d/dockerhup.host.com:5000/
echo "certificate strinig" > /etc/docker/certs.d/dockerhup.host.com:5000/ca.crt
docker login --username=id --password=password --<email address hidden> dockerhub.host.com:5000

The same should be available for applications that uses docker standalone host, e.g., Kubernetes Cluster (or is it Kubernetes Cluster?)

Revision history for this message
Peng Wu (wu105) wrote :

for the dockerhub default repository, we may also need to provide ids/passwords for the private repositories hosted there.

Changed in murano:
importance: Undecided → Wishlist
milestone: none → newton-1
affects: murano → murano-apps
Changed in murano-apps:
milestone: newton-1 → none
milestone: none → newton-1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.