summaryrefslogtreecommitdiff
path: root/vendor
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2020-05-18 12:54:40 -0600
committerValentin Rothberg <rothberg@redhat.com>2020-05-20 10:22:16 +0200
commit973d6244189133b14c8cb77c6b377fb2b2a1501f (patch)
tree2570590e3be2bf68d9f9080ce75a2f62ae658734 /vendor
parent4eee0d840f0af81560d89864ea64b95c9e70b18d (diff)
downloadpodman-973d6244189133b14c8cb77c6b377fb2b2a1501f.tar.gz
podman-973d6244189133b14c8cb77c6b377fb2b2a1501f.tar.bz2
podman-973d6244189133b14c8cb77c6b377fb2b2a1501f.zip
New tool: hack/podman-registry, manages local registry
In response to #6207: this is a helper script intended for use in starting and stopping a local container registry. It takes care of port, username, password assignments; generates a self-signed certificate; and starts the container in an isolated podman root/runroot to avoid conflicting with the caller's environment. Intended usage: invoke from shell script, using 'eval' to get results into calling process environment. See help message (-h) for invocation details. This will work for shell scripts but will be difficult if called from Go or C - if that is likely to happen, I'd love to hear suggestions for alternate ways to get the settings back to the caller. Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'vendor')
0 files changed, 0 insertions, 0 deletions