Options parameter is passed through to the underlying command. Separated names) must be specified using the image parameter. This runs docker rmi on the registry machine. Remove images from the registry with the rmi action: juju run-action -wait docker-registry/0 rmi \ ForĮxample, show non-truncated output with numeric image IDs: juju run-action -wait docker-registry/0 images \ Repository parameters are passed through to the underlying command. This runs docker images on the registry machine. List images known to the registry with the images action: juju run-action -wait docker-registry/0 images \ The image tag can be overriden by specifying the tag action parameter. Http-host config option or if config is not The default image tag is 'net_loc/name:version', where 'net_loc' is the Given image and subsequently tag/push it. Specifying pull=True (the default), the action will first pull the This action will always tag and push a local image to the registry. This charm provides the push action to do this: juju run-action -wait docker-registry/0 push \ To make an image available in the deployed registry, it must be tagged and See the Private Docker Registry documentation for details on This charm supports monitoring with nagios: juju deploy cs:~containers/docker-registry ca.crt haproxy/$UNIT_NUM:/etc/docker/registry Juju scp docker-registry/$UNIT_NUM:/etc/docker/registry/ca.crt. Juju run -unit haproxy/$UNIT_NUM 'chown ubuntu:ubuntu /etc/docker/registry' For example: juju run -unit haproxy/$UNIT_NUM 'mkdir -p /etc/docker/registry' The path to theĬA must match on both registry and proxy units. To the proxy so the registry certificate can be verified. You will need to transfer the registry CA certificate TLS is supported between haproxy and docker-registry, though some manualĬonfiguration is required. Note: HA deployments require the proxy to be in active-passive peering Will fail over to a backup if the primary service becomes unavailable. This provides a highly available deployment that When multiple docker-registry units are deployed, the proxy will beĬonfigured with one unit chosen as the primary proxied service with remaining Juju add-relation haproxy docker-registry This is achieved byĭeploying and relating to a proxy provider, such as haproxy: juju deploy cs:~containers/docker-registry This charm supports an http proxy relation that allows operators toĬontrol how the registry is exposed on the network. The configured tls-*-blob data will be written to correspondingĬonfigured tls-*-path files: juju config docker-registry \ Juju scp /my/local/cert.key docker-registry/0:/home/ubuntu/cert.keyįinally, custom TLS data may be provided as base64-encoded config options to Juju scp /my/local/cert.crt docker-registry/0:/home/ubuntu/cert.crt This charm as follows: juju scp /my/local/ca.pem docker-registry/0:/home/ubuntu/ca.pem Instead, transfer required files and configure This charm also supports configuration-based TLS, which does not require a Juju add-relation easyrsa docker-registry This canīe enabled by deploying and relating to a TLS provider, such as easyrsa: juju deploy cs:~containers/docker-registry This charm supports TLS via the tls-certificates relation. Standalone Registryįor testing purposes, a simple, insecure registry can be deployed with: juju deploy cs:~containers/docker-registry With clients that implement the docker-registry interface. The registry is deployed as a stand alone application and supports integration This charm provides a registry for storage and distribution of docker images.
0 kommentar(er)
