e69d879cae
We spawn socat processes in the background in buildset registry related roles. Ansible 5 is much better at killing all processes in its session when the task is complete. Work around that by starting socat within a new session with setsid. Change-Id: Iaab17f5d4068be6b08e3d89d2abe80199f0cd654 |
||
|---|---|---|
| .. | ||
| defaults | ||
| tasks | ||
| templates | ||
| README.rst | ||
README.rst
Runs a container registry for the use of this buildset.
This may be used for a single job running on a single node, or it may be used at the root of a job graph so that multiple jobs running for a single change can share the registry.
Role Variables
Return Values
Information about the registry.
The host (IP address) of the registry.
The port on which the registry is listening.
The username used to access the registry via HTTP basic auth.
The password used to access the registry via HTTP basic auth.
The (self-signed) certificate used by the registry.